Scrape all tweets from a Twitter/X thread on a tweet detail page (/status/ URL), collecting the author's tweets and returning individual and merged text.
Scrape all tweets from a Twitter/X thread. Must be on a tweet detail page (/status/ URL). Collects all tweets by the same author, returns individual tweets and merged text.
| Name | Required | Description | Default |
|---|---|---|---|
| maxScrolls | No | Maximum scroll attempts to load more tweets |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses that it collects all tweets by the same author and returns both individual tweets and merged text, which is real behavioral context. However, it says nothing about auth, rate limits, or how scrolling failure is handled, so it is only partially transparent.
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?
Three short sentences: purpose, precondition, output shape, in that order. No filler, and the critical scoping constraint is front-loaded after the core purpose.
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?
No output schema exists, and the description compensates by describing the return shape (individual tweets + merged text). The single-parameter surface is simple and the precondition is stated, but auth/rate-limit behavior is absent.
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 coverage is 100% and maxScrolls is fully documented in the schema, so the description adds no parameter detail. Baseline 3 applies when the schema already does the work.
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?
States a specific verb ('scrape') and resource ('all tweets from a Twitter/X thread'), plus the scope of what is collected. It implicitly separates itself from scrape_timeline/scrape_bookmarks by the 'thread' scope and the detail-page precondition, but 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a hard precondition — 'Must be on a tweet detail page (/status/ URL)' — which tells the agent exactly when this tool is usable. It stops short of naming alternatives (e.g. scrape_current_view) or saying when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.