Extract tweets from a Twitter/X timeline, including text, author, metrics, and URLs. Navigate to the timeline first if needed.
Scrape tweets from the Twitter/X timeline. Returns tweet text, author, metrics, and URLs. Navigate to the timeline first if not already there.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of tweets to collect | |
| scrollAttempts | No | Number of 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 provided, the description must carry the full behavioral burden. It discloses that navigation to the timeline may be required, which is useful. But it does not mention permissions, rate limits, side effects, or scrolling/pagination behavior beyond the schema parameters.
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?
Two short sentences, front-loaded with the core action, followed by return contents and a prerequisite. Every sentence earns its place.
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?
For a two-parameter scraping tool with complete schema coverage and no output schema, the description covers purpose, returns, and one prerequisite. It is adequate overall, though it could better distinguish usage from similar scrape siblings.
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?
The schema already documents both parameters with 100% description coverage, including defaults and meanings. The description adds no parameter-specific details, so baseline 3 is appropriate.
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?
The description states a specific verb and resource: 'Scrape tweets from the Twitter/X timeline.' It also lists the return contents, clearly distinguishing it from siblings such as scrape_search_results, scrape_bookmarks, and scrape_thread.
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?
It gives one usage condition: 'Navigate to the timeline first if not already there.' However, it does not explain when to choose this tool over scrape_current_view or other scrape tools, nor 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.