Skip to main content
Glama

XCROP X (Twitter) data

Get X profile

get_user
Read-only

Profile of an X (Twitter) account: name, bio, followers, following, post count, verification, creation date. Costs 18 credits.

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": {
      "username": "<username>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesX username without @, e.g. elonmusk

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuinely useful non-annotation fact, the 18-credit cost, which supports budget-aware calling, but says nothing about failure modes (nonexistent, suspended, or protected accounts), rate limiting, or data freshness.

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; the returned fields are front-loaded and the cost caveat follows immediately. Nothing could be removed without losing information.

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 one-parameter read tool with full schema coverage, annotations, and no output schema, the definition covers what the call returns and what it costs. The remaining gap is error behavior, which matters somewhat for an open-world lookup of a handle that may not exist.

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%: the single parameter is documented with format and an example ('without @, e.g. elonmusk'), so the schema carries the load. The description adds no parameter meaning beyond that, which is the baseline case.

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 uses a specific resource ('Profile of an X (Twitter) account') and enumerates exactly what is returned (name, bio, followers, following, post count, verification, creation date), so an agent knows precisely what this call yields. It does not name or contrast any sibling (e.g. search_users or get_followers), so it falls short of full differentiation.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is mentioned. The only decision signal offered is indirect: the 18-credit cost hints that it should not be called frivolously, but the agent must infer that itself.

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