Skip to main content
Glama
X Use

X Use

by felixlark

Read an X conversation

x_thread
Read-onlyIdempotent

Resolve a post URL or status ID to its conversation and retrieve posts from that thread, with recent or full scope options and pagination for read-only thread analysis.

Instructions

Resolve a post's conversation_id and read posts in that conversation. Recent scope only covers the last 7 days; full scope may be forbidden. 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": {
      "post": "<post>"
    },
    "name": "x_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesAny post URL or numeric status ID in the conversation.
scopeNorecent
expansionsNoX API expansions, for example author_id,attachments.media_keys,referenced_posts.
max_resultsNoRecent search accepts 10-100; full-archive search accepts 10-500.
poll_fieldsNoMapped to poll.fields.
post_fieldsNoMapped to the current query parameter post.fields.
user_fieldsNoMapped to user.fields.
media_fieldsNoMapped to media.fields.
place_fieldsNoMapped to place.fields.
pagination_tokenNoOpaque next_token from a previous thread page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the 'Read-only' sentence is partly redundant. The description nonetheless adds real behavioral context beyond the annotations: the 7-day recency window and the possibility that full-archive access is forbidden, which matters for planning and error handling.

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?

Three short sentences, front-loaded with the core action, with no filler. The 'Read-only' sentence repeats the annotation hints and lightly dilutes the otherwise dense payload.

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 10-parameter tool with no output schema, the description says nothing about what is returned (posts, conversation shape) or how pagination_token is used to continue reading a thread. The scope constraint is covered well, but the read/pagination behavior an agent needs to plan multi-page calls is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 90%, so the baseline is 3, but the description adds genuine meaning to the scope enum by mapping recent to a 7-day window and warning that all may be forbidden. It leaves pagination_token and the field-expansion parameters entirely to the schema, which is acceptable given the high coverage.

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?

States a specific two-step action: resolve a post's conversation_id, then read posts in that conversation. An agent can distinguish this from x_search or x_user_posts by the conversation-scoped framing, though the description never names those siblings 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?

Adds useful usage conditions for the scope parameter (recent = last 7 days, full scope may be forbidden), which effectively tells the agent to default to recent. However, there is no guidance on when to pick this tool over x_search or x_user_posts for gathering posts.

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