Extract currently visible X timeline posts (up to 20) with author, text, status URL, and social action labels for monitoring or analysis.
Extract the currently visible X timeline posts with author, text, status URL, and social action labels.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max number of visible posts to extract (1-20). |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full burden. It says 'currently visible' which implies scoping to rendered DOM state, but does not disclose whether scrolling is required, whether extraction is read-only/no side effects, or any rate/visibility constraints.
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?
One front-loaded sentence with no filler. The list of returned fields is compact and useful. Slightly light on context given the crowded sibling environment.
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 simple one-param extractor with no output schema and no annotations, the description covers the what and the return fields. It omits when to use it versus the many sibling extract/search tools and any behavioral constraints, leaving clear gaps.
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 the single 'limit' parameter is fully documented in the schema with its 1-20 range. The description adds nothing about the parameter. 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?
States a specific verb (Extract) and resource (currently visible X timeline posts) and lists returned fields. Does not name a sibling or differentiate against x_get_profile_posts, x_get_community_feed, or x_extract_post, which is the main gap.
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?
No when-to-use guidance or alternatives mentioned. With 37 siblings, an agent must infer from the name alone that this is for the home timeline vs profile or community feeds.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.