Retrieve an X user record by username from the x-users dataset. Provide a username with or without @ to fetch matching profile data.
Get an X user from the dataset. Returns one X user record by username from dataset id enum value x-users.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | X username, with or without a leading @, max 128 characters |
Changes observed during successful MCP inspections.
v1.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states it returns one record, but does not disclose read-only nature, error handling, rate limits, or what happens if the username is not found.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action, no wasted words. Efficient and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description covers the basic purpose and dataset id. However, it lacks details about the return format or any edge cases, making it adequate but not thorough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the schema already describes the username parameter. The description adds 'by username' which is redundant. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'an X user from the dataset', specifying it returns one record by username from dataset id 'x-users'. This distinguishes it from sibling tools like datasets_x_users_search and datasets_x_users_facets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving a single user by username, but does not explicitly state when to use this tool versus alternatives like datasets_x_users_search, nor does it provide exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.