Skip to main content
Glama

XCROP X (Twitter) data

Search accounts

search_users
Read-only

Find X accounts by name or keyword. Costs 18 credits per account returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many accounts to return (default 10, max 50)
queryYesName or keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 new context by disclosing a per-result credit cost of 18, which matters for call budgeting. It does not explain result ordering, pagination, or whether the query supports search operators, leaving some behavioral gaps.

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 short sentences with zero filler: capability first, cost second. Every sentence carries distinct information and nothing is repeated from the schema.

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

Completeness4/5

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

For a two-parameter read tool with full schema coverage, complete annotations, and no output schema, the definition covers purpose, matching mode, and cost. Minor gaps remain around result ordering and whether the query accepts advanced syntax, but nothing essential to invoking it correctly is missing.

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 coverage is 100%, so both parameters (query, count with default/min/max) are already fully documented in structured form. The description only restates "by name or keyword" and does not add syntax, operator, or matching-semantics detail beyond the schema.

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?

States a specific verb and resource ("Find X accounts") plus the matching mechanism ("by name or keyword"), which implicitly separates it from lookup-style siblings like get_user. It never names an alternative explicitly, so differentiation is inferred rather than declared.

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

Usage Guidelines3/5

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

The "by name or keyword" phrasing implies discovery-style searching rather than ID lookup, giving some implicit routing signal against get_user. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources