AIsa X / Twitter

Get User About Info

get_twitter_user_about

Read-onlyIdempotent

Get the extended 'About this account' panel for an X user by @handle. Use this for provenance and trust checks — it surfaces signals the standard profile does not, such as the account's country, verification details, and username-change history. Returns a single profile object under data. For the standard profile (bio, follower counts, avatar), use get_twitter_user_info instead.

Published reference price: $0.00018 USD per successful request. Account-specific pricing and final settlement may differ.

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_twitter_user_about"
  }
}

Input Schema

Name	Required	Description	Default
`userName`	Yes	The screen name of the user

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description still adds real value beyond that: what the panel surfaces (country, verification details, username-change history) and the shape of the return ('a single profile object under `data`'). It does not mention auth or rate limits, but the annotation bar is met with useful extra context.

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?

Three front-loaded sentences with zero waste: purpose, use case, return shape, and sibling routing in order of importance. The appended pricing block is boilerplate, not part of the authored description.

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

Completeness5/5

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

An output schema exists, so return values need not be enumerated, yet the description still notes the `data` wrapper. For a one-parameter read tool with rich annotations, everything an agent needs to select and call it correctly is present.

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 the single userName parameter is fully documented by the schema; baseline is 3. The description's 'by @handle' offers a marginally different framing than the schema's 'screen name' but adds no syntax or format detail beyond it.

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

Purpose5/5

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

States a specific verb + resource — fetch the extended 'About this account' panel for an X user by @handle — and explicitly contrasts it with the sibling get_twitter_user_info. An agent can distinguish this from the standard-profile tool without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('provenance and trust checks') and names the alternative with its selecting condition ('For the standard profile (bio, follower counts, avatar), use get_twitter_user_info instead'). Nothing is left to inference.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?