PostPod

Create script audio

create_script_audio_job

Debit prepaid credits and queue audio for a script. The price matches estimate_script_audio. A low balance returns 402. Pass idempotency_key to retry without a second debit. Set confirm_another when you mean to pay for another job. The audio has no intro or outro.

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": {
      "script": "<script>",
      "voice": "<voice>"
    },
    "name": "create_script_audio_job"
  }
}

Input Schema

Name	Required	Description
`voice`	Yes	Narrator display name or lowercase id: Nora, Leo, Kristine, Ken, or Marko.
`script`	Yes	The words to speak.
`input_language`	No	auto or a language code. Defaults to auto.
`confirm_another`	No	Set true to pay for another job while one is still running, or to submit the same script again within 15 minutes.
`idempotency_key`	No	Optional retry key, 8 to 80 letters, numbers, underscores, or hyphens. The same key does not debit twice.
`output_language`	No	Language code for the spoken audio. Defaults to English (en).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, it discloses the credit debit, the pricing relationship to estimate_script_audio, the 402 low-balance failure mode, retry safety via idempotency_key, and the confirm_another guard for concurrent or repeated submissions. It also states the output shape ('no intro or outro'), which annotations cannot convey.

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?

Five short sentences, each carrying a distinct fact (cost, price parity, error code, retry key, confirm_another, output shape), with the cost consequence front-loaded. No filler or restatement of the name.

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 mutating, credit-consuming tool with no output schema, it covers cost, failure mode, retry safety, and the human-facing trigger. The remaining gap is that it never says what the call returns or which sibling to use for job status/download, which an agent will need immediately after.

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 coverage is 100%, so voice, script, languages, confirm_another, and idempotency_key are already documented in the schema. The description restates the idempotency and confirm_another semantics rather than adding new format or constraint detail, so the baseline 3 applies.

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 first sentence gives a specific verb pair and resource ('Debit prepaid credits and queue audio for a script'), which distinguishes this from estimate_script_audio by making clear it is the paying/enqueuing step rather than the pricing step. An agent can tell what the tool does without opening the schema.

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

Usage Guidelines4/5

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

It gives concrete when-conditions: pass idempotency_key to retry, set confirm_another to pay for another job, and it flags the 402 outcome for a low balance. It does not explicitly route the agent to estimate_script_audio beforehand or to get_script_audio_job for polling, so the guidance is clear but not exhaustive.

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

All PostPod 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?