Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_x_users_search

Search public X (Twitter) profiles using full-text queries, filters like follower count, verification, and bio presence, then sort by relevance or follower count to find matching accounts.

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.

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

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral transparency burden. It only adds that profiles are public and stored in a search index; it does not disclose whether the operation is read-only, what the default sort is, how pagination behaves, or what the response looks like. The sort enum adds no value because it is already present 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.

Conciseness3/5

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

The description is short and front-loaded with the core search action. However, the first sentence largely restates the tool name, and the third sentence redundantly duplicates the sort enum already in the schema; not every sentence earns its place.

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

Completeness2/5

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

For a tool with 17 optional parameters and no output schema, the description is too thin. It does not describe return shape, default sort behavior, pagination semantics, or how q interacts with the many filters. An agent can infer it returns matching profiles but cannot anticipate key calling behavior or response structure.

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 baseline is 3 even though the description adds no parameter-level meaning. The sort enum is repeated verbatim from the schema without explaining defaults or interaction effects, so there is no bonus for additional semantic value.

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: searching the X users dataset of public X/Twitter profiles via a search index. This helps distinguish it from item-lookup and facets siblings, though it never names alternatives like datasets_x_users_item or datasets_x_users_facets explicitly.

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?

No guidance is given for when to use this tool versus related dataset tools or x_profile. The phrase 'search index' implies a search use case, but the description provides no explicit when-to-use, when-not-to-use, or alternative-selection guidance.

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