Skip to main content
Glama

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. A 409 script_audio_active includes job_id and job_url. The message says you have already paid only when that job was charged. Otherwise it says you already have audio being made. A queued job with no progress for more than 30 minutes, or a render with no progress or heartbeat for 2 hours, is failed before that 409. The audio has no intro or outro. Narrators are Nora, Leo, Kristine, Ken, and Marko.

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

NameRequiredDescriptionDefault
voiceYesNarrator display name or lowercase id: Nora, Leo, Kristine, Ken, or Marko.
scriptYesThe words to speak.
input_languageNoauto or a language code. Defaults to auto.
confirm_anotherNoSet true to pay for another job while one is still running, or to submit the same script again within 15 minutes.
idempotency_keyNoOptional retry key, 8 to 80 letters, numbers, underscores, or hyphens. The same key does not debit twice.
output_languageNoLanguage code for the spoken audio. Defaults to English (en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare this is a non-read-only, non-destructive mutation; the description goes far beyond by disclosing the credit debit, the 402 low-balance response, the 409 script_audio_active payload with job_id and job_url, and the distinction between the two 409 messages depending on whether that job was charged. It also defines staleness rules (30 minutes queued, 2 hours rendering without heartbeat) and notes the audio has no intro or outro, which materially affects what the agent should expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The charging action and its cost relationship are front-loaded, and the error-handling sentences are dense but each carries operational value. The closing narrator list ("Nora, Leo, Kristine, Ken, and Marko") duplicates the voice parameter's schema description verbatim and is the one clearly redundant sentence.

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 six-parameter mutation with no output schema, the description covers cost, error paths, idempotency, and staleness well enough to call it correctly. The remaining gap is the success response: it never says what a queued job returns (presumably a job_id the agent needs for get_script_audio_job), so an agent must infer the handle from the 409 example.

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 baseline is 3, but the description adds genuine meaning on top: confirm_another is framed as an intent to pay for another job, and idempotency_key is tied to the retry-without-second-debit behavior and the 409 flow. It does not add anything about input_language or output_language beyond what the schema already says, which keeps it from a 5.

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 opening sentence states a specific verb and resource with consequences: "Debit prepaid credits and queue audio for a script." It also distinguishes itself from the sibling estimator by noting "The price matches estimate_script_audio," so an agent can tell quote from commit without opening either 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 clear conditional guidance: pass idempotency_key to retry safely, set confirm_another only when you mean to pay for another job, and points to estimate_script_audio for pricing. What is missing is an explicit statement of when not to call it (e.g. when a job is already active and you do not intend a second charge), though the 409 discussion implies that case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources