Skip to main content
Glama

Xcatcher — Recent X Posts

by io.github.lvpiggyqq

Get accountless crawl payment requirements

get_direct_crawl_payment

Create a request-bound x402 v2 payment requirement for an accountless crawl. Use this only for the accountless x402 path after preflight_crawl; API-key accounts use create_crawl_task instead. Normal requests use progressive batch pricing, so quote the complete deduplicated handle list together. This does not move funds. Return payment_required_b64 unchanged to an x402-compatible wallet/client; the live amount, asset, network, destination, and quoteId are authoritative.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoDirect x402 normal requests use progressive batch pricing; deep is $0.10 per normalized requested handle. Always preflight the complete list.normal
usersYesX handles, @handles, or x.com/twitter.com profile URLs.

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 / mode / description
      Previous value: -"normal costs 1 point-equivalent per handle; deep costs 10."New value: +"Direct x402 normal requests use progressive batch pricing; deep is $0.10 per normalized requested handle. Always preflight the complete list."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses that the tool does not move funds and that the returned payment_required_b64 should be passed unchanged to an x402-compatible wallet/client. Clarifies that the live amount, asset, network, destination, and quoteId are authoritative, adding valuable behavior beyond 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?

Four sentences, each carrying essential information: purpose, usage constraints, pricing behavior, and return handling. No redundant phrases or filler.

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 output schema exists, the description covers the full workflow: when to use, how to prepare inputs, what the response contains, and how to interpret it. The pricing distinction between normal and deep mode is also explained, making it self-sufficient.

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 coverage is 100% and includes detailed descriptions for both parameters, so baseline is 3. The description adds extra semantic value by instructing to deduplicate the handle list and quote it together, which is not explicitly in 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 clearly states the tool creates a request-bound x402 v2 payment requirement for an accountless crawl. It differentiates from sibling tools by explicitly naming the accountless x402 path and contrasting with create_crawl_task for API-key accounts.

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 when and when-not to use: 'Use this only for the accountless x402 path after preflight_crawl; API-key accounts use create_crawl_task instead.' It also gives operational guidance about progressive batch pricing and quoting the complete deduplicated handle list.

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