Skip to main content
Glama

Xcatcher — Recent X Posts

by io.github.lvpiggyqq

Preview crawl results

get_result_preview
Read-only

Return up to 100 result rows from an API-key account task as native structured JSON for direct agent analysis; accountless x402 tasks use get_direct_result_preview instead. Use offset/next_offset for pagination; this does not download or parse XLSX. Use after has_result=true; use get_result_download_url when the complete XLSX is required. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum result rows to return (1-100).
offsetNoZero-based row offset for pagination.
task_idYesCompleted task ID owned by the current API key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

While annotations already declare readOnlyHint=true, the description adds valuable behavioral context: it does not download or parse XLSX, returns up to 100 rows, and is safe to use after has_result=true. These specifics go beyond what annotations convey, though auth details and rate limits are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (3 sentences), front-loaded with the core purpose, and each sentence adds distinct value (function, alternative, caveat). No redundant or filler text.

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 the presence of an output schema, the description covers return values implicitly. It handles pagination, preconditions, alternatives, and thread-safety (read-only) comprehensively. This is a complete picture for an agent to select and invoke the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100% with detailed parameter descriptions (limit, offset, task_id). The description reinforces 'up to 100 rows' and 'offset/next_offset' but doesn't add substantive new meaning beyond what the schema already provides, so a baseline 3 is appropriate.

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 action (Return), resource (result rows from an API-key account task), and output format (native structured JSON). It explicitly distinguishes from sibling tools such as get_direct_result_preview for accountless x402 tasks, making it unambiguous.

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?

Provides explicit usage context: when to use (after has_result=true), when to avoid (accountless x402 tasks, use get_direct_result_preview), and alternative for complete XLSX (get_result_download_url). Also mentions pagination via offset/next_offset. This is comprehensive guidance.

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

All Xcatcher — Recent X Posts toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, with explicit guidance for when to use accountless vs API-key variants. Even closely related tools like get_task_status and wait_for_task are differentiated by their polling behavior, so an agent can reliably select the correct one.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern in snake_case (create_crawl_task, get_task_status, list_crawl_tasks). The one exception is x402_topup, which places the protocol prefix before the verb, breaking the pattern slightly but still remaining readable.

Tool Count4/5

With 17 tools, the count is slightly above the typical 3-15 range, but the service supports two distinct payment paths (API-key and accountless x402), each requiring a parallel set of status/result tools. The count feels justified by the scope, with no obvious bloat.

Completeness5/5

The tool set covers the full lifecycle of creating, monitoring, retrieving, and managing crawl tasks, including both payment flows. It includes task creation, status polling, result preview/download, cancellation, listing, balance checks, and payment top-ups, leaving no critical gaps for the stated purpose.

Resources