Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_user_about

Get user 'about' details. Extra profile details of a user (account location, creation info, verification details).

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": "x_user_about"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNameYesScreen name without the @, e.g. `NASA`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the kind of data returned, and "Get" implies a read, but it says nothing about error behavior for a nonexistent or protected account, permission/suspended-account constraints, or rate limits — all relevant for a public-data lookup tool.

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?

Two short sentences, front-loaded with the action and followed by the payload contents. There is slight overlap between "'about' details" and "Extra profile details," but no meaningful waste.

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 one-parameter read tool with no output schema, the description covers what data comes back, which is the main thing an agent needs. What it lacks is differentiation from the closely named sibling x_user_info, leaving the agent to guess which profile endpoint to call.

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% and the single userName parameter is fully documented in the schema, including the no-@ format and an example. The description adds nothing about the parameter, which is acceptable given the schema already does the work — baseline 3.

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 gives a specific verb+resource ("Get user 'about' details") and then enumerates the payload (account location, creation info, verification details), so the agent knows what this returns. It hints at being supplementary ("Extra profile details") but never names x_user_info, so the boundary with the sibling profile tool must be guessed.

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 word "Extra" implies this should be used when additional profile metadata beyond the basic user info is needed, but that is only implied. There is no explicit when/when-not statement, no mention of x_user_info as the alternative, and no prerequisites.

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