Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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.

Instructions

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over username, name, bio and location, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, followers_desc, followers_asc, crawled_at_desc, crawled_at_asc, created_at_desc, created_at_asc
has_bioNoFilter by a non-empty profile bio
usernameNoExact username filter (case-insensitive), max 128 characters
max_ratioNoMaximum follower-to-following ratio
min_ratioNoMinimum follower-to-following ratio (low values surface follow-spam / bot-like accounts)
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
source_tierNoExact filter for which seed tier discovered this account, e.g. github-users, wikidata, tiktok-creators, journalists
crawled_afterNoRecords last refreshed on or after this date (RFC3339 or YYYY-MM-DD)
created_afterNoAccounts created on or after this date (RFC3339 or YYYY-MM-DD)
max_followersNoMaximum follower count
min_followersNoMinimum follower count
crawled_beforeNoRecords last refreshed on or before this date (RFC3339 or YYYY-MM-DD)
created_beforeNoAccounts created on or before this date (RFC3339 or YYYY-MM-DD)
has_external_urlNoFilter by a linked external URL
is_blue_verifiedNoFilter by the X blue-check verification flag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "followers_desc",
+  "followers_asc",
+  "crawled_at_desc",
+  "crawled_at_asc",
+  "created_at_desc",
+  "created_at_asc"
+]
  2. Addedv1.6.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a real behavioral trait: the credit-based billing model (1 credit/record, minimum 2, 100 per full page). That is genuinely useful cost context an agent cannot get elsewhere. It still omits auth requirements and return-shape/pagination behavior, so not a 5.

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

Conciseness4/5

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

Front-loaded with purpose, then behavior. The sort enum listing is redundant with the schema and occupies real space, but the billing sentence earns its place. Overall efficient though slightly padded by the enum repetition.

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

Completeness3/5

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

For a 17-parameter tool with no output schema and no annotations, the description supplies billing and sorting context but says nothing about the response contents, pagination mechanics beyond the schema constraint, or rate/auth behavior. Adequate but leaves gaps an agent may need.

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%, so the schema already documents all 17 parameters including the sort enum and ratio semantics. The description's restatement of the sort enum adds nothing beyond the schema, and the billing note is not a parameter-level detail. Baseline 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: 'Search the X users dataset' / 'Searches public X (Twitter) user profiles stored in a search index.' An agent can tell this is a full-text/filtered search over X users. It does not explicitly distinguish itself from siblings like datasets_x_users_facets or datasets_x_users_item, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as the facets or item siblings. The sort enum hints at ranking use cases but nothing tells the agent when this tool is the right choice versus other X-user tools.

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

Deploy Server

Other Tools