Skip to main content
Glama

X (Twitter) profile

x_profile
Read-only

Twitter API: User Profile: one public X (Twitter) account by handle or x.com URL: display name, bio, followers, following, post count, verification, avatar link and creation time, in the shared social schema. Bad input is free; not found or no match is not charged. Price: $0.02 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "handle": "<handle>"
    },
    "name": "x_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesAn X handle (with or without @) or an x.com profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint). The description adds genuinely useful context beyond them: $0.02 per successful call, payment passed in _meta["x402/payment"], and that bad input and not-found results are free. It does not say what a not-found response looks like or whether repeated calls re-bill, which matters given idempotentHint=false.

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?

Front-loaded with purpose and returned fields, then the cost and payment mechanics; every clause carries information. The colon-chained run-on style and the 'Bad input is free; not found is not charged' fragment make it slightly dense to scan, but nothing is redundant.

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?

With no output schema, listing the returned fields is the right compensation, and the payment/billing prerequisites are disclosed. Remaining gaps are the shape of error/not-found responses and whether repeat calls re-charge, which are minor for a single-parameter read tool.

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 parameter is fully documented there, including acceptance of '@' and full URLs. The description restates the same accepted input forms without adding syntax, normalization, or error-handling details, so the baseline 3 applies.

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 names a specific resource (one public X profile), the input forms (handle or x.com URL), and enumerates the fields returned (display name, bio, followers, verification, etc.). Platform naming separates it from bluesky_profile and instagram_profile, though it never explicitly contrasts with x_posts or x_search, so subtle intra-platform routing is left to inference.

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?

Usage is implied rather than stated: fetch a single account's profile. There is no explicit when-to-use/when-not guidance and no alternative named (e.g., use x_search or social_accounts for discovery), which matters with 25 sibling tools. The pricing/charging conditions do implicitly tell the agent a failed lookup is cheap, which is a weak decision aid.

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.