Skip to main content
Glama

Xcatcher — Recent X Posts

by io.github.lvpiggyqq

Preview accountless paid crawl results

get_direct_result_preview
Read-only

Return structured JSON rows for a completed accountless paid crawl. Use this instead of get_result_preview for an accountless x402 task; API-key accounts use get_result_preview. Use offset for pagination; the task token is required and should be treated as a secret.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return (1-100).
offsetNoZero-based row offset.
task_idYesCompleted paid task ID.
task_tokenYesTask-scoped xtask_ token.

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context by noting the task must be completed, that the token is a secret, and that it returns structured JSON rows. This goes beyond the annotations without contradicting them, warranting a score above baseline.

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 two concise sentences, front-loaded with the primary purpose, followed by alternative usage and parameter guidance. Every sentence contributes value with no redundancy.

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 4-parameter schema, output schema, and annotations, the description covers the essential context: when to use, how to paginate, token secrecy, and the structured return format. It fully equips the 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.

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds a small but meaningful security note about treating task_token as a secret and explicitly mentions using offset for pagination, enhancing parameter understanding beyond the schema.

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 states 'Return structured JSON rows for a completed accountless paid crawl' with a clear verb and resource. It explicitly distinguishes from get_result_preview for API-key accounts, making the tool's specific purpose evident.

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 guidance: 'Use this instead of get_result_preview for an accountless x402 task; API-key accounts use get_result_preview.' It also gives pagination and secret-handling usage notes, leaving no ambiguity about when to invoke this tool.

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