Skip to main content
Glama
XcrapCC

@xcrap/mcp

Official
by XcrapCC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Unroll an X thread

xcrap_get_thread
Read-onlyIdempotent

Unroll any X/Twitter thread from a single post link, returning the original author's posts in order for easy reading or summarization. Excludes replies to focus on the connected chain.

Instructions

Unroll a whole X/Twitter thread from any post in it, returning every post by the original author in order as one readable document.

This is the tool for "read this thread and summarise it". Give it the link the user pasted — first post, last post or anywhere in the middle — and it reconstructs the run. Replies by other people are excluded: a thread is one author's chain, not the surrounding conversation.

When to use this instead of the alternatives:

  • Use this when the link is part of a series of connected posts, or when a single post ends mid-thought.

  • Use xcrap_get_tweet if you only want the one post the URL points at (a thread costs more: 20 calls/minute).

  • Use xcrap_get_user_tweets to read an account's recent posts generally, rather than one connected chain.

Args:

  • url (string, required): any post in the thread, as a URL or numeric id.

  • max_tweets (number, 1-100): how many posts to unroll, default 25. Lower it if a response comes back truncated.

  • format ('markdown' | 'json'): default 'markdown'.

Returns (markdown): the author heading, then every post in order with its timestamp, text and metrics. Returns (json): { root_id, author{...}, count, truncated, tweets[ ] }. The 'truncated' flag is true when the thread is longer than max_tweets.

Note: threads are reconstructed from X's public data, so a very old thread may come back partial — 'truncated' and the post count tell you when that happened.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAny post in the thread, as a URL or numeric id.
formatNoOutput format. 'markdown' (default) is compact, human-readable and costs roughly a tenth of the tokens of the same data as JSON — prefer it for reading and summarising. Use 'json' only when you need exact field access: numeric ids, media URLs, per-metric values, or provenance metadata.markdown
max_tweetsNoMaximum posts to unroll, 1-100 (default 25). Each post costs roughly 200-400 characters of context; lower this if the result is truncated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: 'Replies by other people are excluded', the cost of 20 calls/minute, and the caveat about old threads possibly being partial with the 'truncated' flag. It doesn't mention pagination or exact HTTP details, but it goes beyond annotations with meaningful behavioral notes.

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?

The description is well-structured with a clear first paragraph on purpose, followed by a 'When to use' section, then Args and Returns outlines. It is longer than a minimal description but every part earns its place: the alternative routing, the cost note, and the return format details are all useful. The only minor redundancy is restating schema info like defaults, but it adds value with examples (e.g., 'first post, last post or anywhere in the middle').

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?

Given no output schema, the description compensates by detailing the return formats: markdown has author heading and posts with timestamp/text/metrics; json has root_id, author, count, truncated, and tweets. The 'truncated' flag is explained. Combined with annotations for safety and the comprehensive parameter docs, the description is sufficient for an agent to invoke the tool correctly in typical thread-summarisation scenarios.

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 100%, so the parameters are already described well. The description adds extra value by explaining the purpose: 'url' can be any post in the thread, 'max_tweets' should be lowered if the response comes back truncated, and 'format' has a token-cost comparison that helps the agent decide. This exceeds the schema details without contradicting them, so above the baseline of 3.

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?

The description clearly states the tool unrolls an X/Twitter thread from any post in it, returning all posts by the original author in order as a readable document. It explicitly differentiates from siblings by noting it reconstructs a chain, not a single tweet or an account's general tweets, so an agent can easily select it.

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?

The description provides explicit 'When to use' guidance, including conditions like 'when the link is part of a series of connected posts' and 'when a single post ends mid-thought'. It also clearly states when NOT to use it: use xcrap_get_tweet for a single post, and xcrap_get_user_tweets for general recent posts, with a rationale about cost (20 calls/minute). This is exemplary routing guidance.

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

Deploy Server

Other Tools