AgentX x402 Services (paid MCP tools)

get_podcast_transcript

Read-onlyIdempotent

Full transcript of a podcast episode with published transcript tags (Podcasting 2.0, keyless, deterministic). GET /x402/podcast-transcript?feed=&index=&episode=&format= — $0.02.

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": {
      "feed": "<feed>"
    },
    "name": "get_podcast_transcript"
  }
}

Input Schema

Name	Required	Description
`feed`	Yes	RSS feed URL or Apple Podcasts numeric id
`index`	No	1 = newest episode (as listed)
`format`	No	text \| vtt \| json
`episode`	No	guid or title substring
`payment`	No	Optional. Your x402 payment proof for this exact call — the PAYMENT-SIGNATURE value produced by settling this route's 402 challenge (USDC on Base, Polygon or Solana), or an MPP 'Authorization: Payment ...' value. Omit on a first call: the tool then returns the live 402 challenge to pay against. This server relays your proof upstream and retries; it never creates or settles payments itself.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / payment / description

Previous value: -"Optional. Your x402 payment proof for this exact call — the PAYMENT-SIGNATURE value produced by settling this route's 402 challenge (USDC on Base or Solana), or an MPP 'Authorization: Payment ...' value. Omit on a first call: the tool then returns the live 402 challenge to pay against. This server relays your proof upstream and retries; it never creates or settles payments itself."New value: +"Optional. Your x402 payment proof for this exact call — the PAYMENT-SIGNATURE value produced by settling this route's 402 challenge (USDC on Base, Polygon or Solana), or an MPP 'Authorization: Payment ...' value. Omit on a first call: the tool then returns the live 402 challenge to pay against. This server relays your proof upstream and retries; it never creates or settles payments itself."

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds genuine behavioral context beyond them — "keyless, deterministic" and the $0.02 price — but still omits the 402 payment handshake, which is only explained in the schema's payment property.

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?

Two tight sentences: purpose first, then access mechanics and price. Nothing is padded, and the key facts (tags required, keyless, deterministic, $0.02) are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only fetch tool with a fully covered schema and no output schema, the description conveys the content returned (full transcript plus published tags) and the cost. It could say a bit more about the transcript payload shape per format value, but the essentials are present.

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%, so the schema already documents all five parameters thoroughly. The description adds nothing new per parameter but repeats the query template (feed/index/episode/format), which at least reinforces the required selector. Baseline 3 is appropriate for a fully documented schema, with a small credit for aligning the URL template to the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: "Full transcript of a podcast episode with published transcript tags." This clearly distinguishes it from get_youtube_transcript by media type, though the description never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "with published transcript tags" implies a precondition (only episodes that publish Podcasting 2.0 transcripts will succeed), which is useful implied guidance. However, there is no explicit when-to-use, no advice on using lookup_podcast to resolve a feed/index first, and no guidance on choosing between feed, index, and episode selectors.

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

All AgentX x402 Services (paid MCP tools) 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.

Resources

Need Help?