Xcatcher — Recent X Posts

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "users": "<users>"
    },
    "name": "get_direct_crawl_payment"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Direct x402 normal requests use progressive batch pricing; deep is $0.10 per normalized requested handle. Always preflight the complete list.	normal
`users`	Yes	X handles, @handles, or x.com/twitter.com profile URLs.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 10, 2026

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."

First observedAug 7, 2026

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.