datasets_x_users_search
Search the X users dataset. Searches public X (Twitter) user profiles stored in a search index. Sort enum: relevance, followers_desc, followers_asc, crawled_at_desc, crawled_at_asc, created_at_desc, created_at_asc.
This record as markdown: /tools/crawlora-mcp/datasets-x-users-search.md
What datasets_x_users_search does on Crawlora
AI agents call datasets_x_users_search to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Full-text query over username, name, bio and location, max 256 characters |
page | integer | — | Page number, defaults to 1 |
sort | string | — | Sort enum: relevance, followers_desc, followers_asc, crawled_at_desc, crawled_at_asc, created_at_desc, created_at_asc |
has_bio | boolean | — | Filter by a non-empty profile bio |
username | string | — | Exact username filter (case-insensitive), max 128 characters |
max_ratio | number | — | Maximum follower-to-following ratio |
min_ratio | number | — | Minimum follower-to-following ratio (low values surface follow-spam / bot-like accounts) |
page_size | integer | — | Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000 |
source_tier | string | — | Exact filter for which seed tier discovered this account, e.g. github-users, wikidata, tiktok-creators, journalists |
crawled_after | string | — | Records last refreshed on or after this date (RFC3339 or YYYY-MM-DD) |
created_after | string | — | Accounts created on or after this date (RFC3339 or YYYY-MM-DD) |
max_followers | integer | — | Maximum follower count |
Parameters from the server's own tool schema.
Why datasets_x_users_search is rated Low
This is a read-only operation that queries an existing dataset of public X user profiles. It retrieves information without creating, modifying, deleting, or executing any operations. The sort parameters are purely presentational. The data is public, and searching it poses minimal risk—it is a standard query operation with no destructive, financial, or execution capabilities.
From the tool's definition The tool 'searches public X (Twitter) user profiles stored in a search index' with sort options like 'relevance', 'followers_desc', etc. The verb 'search' and description 'Searches' clearly indicate data retrieval with no modifications or side effects.
Risk signalsHigh parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs datasets_x_users_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datasets_x_users_search, this is the rule to start with:
datasets_x_users_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every datasets_x_users_search call is checked against it from then on.
Questions about datasets_x_users_search
Search the X users dataset. Searches public X (Twitter) user profiles stored in a search index. Sort enum: relevance, followers_desc, followers_asc, crawled_at_desc, crawled_at_asc, created_at_desc, created_at_asc. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_x_users_search accepts 12 parameters: q, page, sort, has_bio, username, max_ratio, min_ratio, page_size, source_tier, crawled_after, created_after, max_followers. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for datasets_x_users_search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Crawlora. Nothing to install.
datasets_x_users_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the datasets_x_users_search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for datasets_x_users_search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
datasets_x_users_search is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue