Skip to main content
Glama
X Use

X Use

by felixlark

Look up an X user

x_user
Read-onlyIdempotent

Look up an X user by @username, username, or numeric user ID to retrieve read-only profile data for account research and verification.

Instructions

Look up an X user by @username, username, or numeric user ID. Read-only.

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": {
      "user": "<user>"
    },
    "name": "x_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUsername with optional @, or numeric user ID.
expansionsNoX API user expansions such as pinned_post_id.
post_fieldsNoMapped to post.fields for expanded posts.
user_fieldsNoMapped to user.fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so "Read-only" merely restates structured data and earns no credit. Nothing is added about failure behavior for unknown users, rate limits, or default response shape, which is what the description could have contributed.

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, identifier format front-loaded, no filler. Every word carries information about what the tool does or what it costs.

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?

A simple keyed lookup with full schema documentation and rich annotations; no output schema exists, so return values need not be described. Only minor gap is that the pass-through nature of the expansion/field parameters is left entirely to the schema.

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 baseline is 3. The one clause about identifier formats duplicates the schema's own description of `user`, and expansions/post_fields/user_fields get no added meaning from the description.

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?

"Look up an X user" gives a specific verb and resource, and the description enumerates the accepted identifier forms (@username, username, numeric ID). It separates itself from x_user_posts by scoping to the user object rather than content, though it never names a sibling explicitly.

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 identifier forms imply when the tool applies, but there is no explicit when-to-use versus x_user_posts or x_search, and no exclusion or prerequisite stated. Guidance is inferable rather than given.

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