Skip to main content
Glama

Xcatcher — Recent X Posts

by io.github.lvpiggyqq

Get accountless paid task status

get_direct_task_status
Read-only

Read an accountless paid crawl using its task_id and task-scoped token. Use this instead of get_task_status for an accountless x402 task. Poll every 5-10 seconds until task.has_result is true or it reaches failed/cancelled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID returned after x402 settlement.
task_tokenYesTask-scoped xtask_ token returned after settlement or idempotent recovery.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / task_token / description
      Previous value: -"Task-scoped xtask_ token returned once after settlement."New value: +"Task-scoped xtask_ token returned after settlement or idempotent recovery."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds behavioral details: polling interval, expected fields (task.has_result), and terminal states (failed/cancelled). No contradiction with annotations.

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?

Three concise sentences deliver the necessary context without fluff. Every sentence contributes to understanding purpose, usage, or expected behavior.

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?

With an output schema available, the description correctly avoids repeating return details. It covers the core use case, alternative tool, and polling behavior, providing complete context for correct invocation.

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 provides complete descriptions for both parameters (task_id and task_token). The description only restates them without adding meaningful extra semantics beyond what the schema already covers, so 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?

Description clearly states the verb 'Read' and resource 'accountless paid crawl', and distinguishes it from get_task_status by naming the alternative. This makes the tool's purpose specific and 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?

Explicitly instructs to use this tool instead of get_task_status for accountless x402 tasks and provides polling cadence (every 5-10 seconds) and termination conditions. This gives clear when-to-use and how-to-use 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