Crawlora MCP

datasets_x_users_search

Read-only

Search the stored public X (Twitter) user profile dataset using a query and filters. Results are indexed user records, not live profile fetches; use the item endpoint when you have a record ID.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Optional full-text query over username, name, bio and location, max 256 characters.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort order. Allowed values: relevance, followers_desc, followers_asc, crawled_at_desc, crawled_at_asc, created_at_desc, created_at_asc. Defaults to relevance with q, otherwise followers_desc.
`has_bio`	No	Optional filter for a non-empty profile bio.
`username`	No	Optional exact username filter (case-insensitive), max 128 characters.
`max_ratio`	No	Optional maximum follower-to-following ratio, 0 or greater.
`min_ratio`	No	Optional minimum follower-to-following ratio, 0 or greater. Low values surface follow-spam / bot-like accounts.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`source_tier`	No	Optional exact filter for which seed tier discovered this account, e.g. github-users, wikidata.
`crawled_after`	No	Optional filter for records last refreshed on or after this date (RFC3339 or YYYY-MM-DD).
`created_after`	No	Optional filter for accounts created on or after this date (RFC3339 or YYYY-MM-DD).
`max_followers`	No	Optional maximum follower count, 0 or greater.
`min_followers`	No	Optional minimum follower count, 0 or greater.
`crawled_before`	No	Optional filter for records last refreshed on or before this date (RFC3339 or YYYY-MM-DD).
`created_before`	No	Optional filter for accounts created on or before this date (RFC3339 or YYYY-MM-DD).
`has_external_url`	No	Optional filter for a linked external URL.
`is_blue_verified`	No	Optional filter for the X blue-check verification flag.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond them by clarifying results come from a stored, indexed dataset rather than live profile fetches, which affects freshness expectations. It does not touch pagination ceilings or rate limits, but those live in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both load-bearing: the first states the operation and scope, the second disambiguates from live fetches and routes to the item endpoint. Nothing is padded and the key scoping fact is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, full annotation coverage, and 100% schema description coverage on 17 parameters, the description's job is narrow and it fulfills it: identify the dataset, flag the indexed-not-live nature, and route to the item endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across all 17 optional parameters, so the schema fully documents query, filters, sort, and paging. The description adds only the vague phrase 'using a query and filters' and no syntax or semantics beyond the schema, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and a precisely scoped resource (the stored public X/Twitter user profile dataset), and immediately clarifies that these are indexed records rather than live fetches. This distinguishes it cleanly from the item endpoint sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing guidance: use this tool with a query and filters, and switch to the item endpoint when you already hold a record ID. It does not mention the facets sibling or when facets should precede a search, so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?