Skip to main content
Glama

PostPod

Generate episode

generate_episode
Idempotent

Start today's episode for this show. Uses the same Free and Pro rules as the website: one episode per delivery day, the same deleted-day tombstone, and the same pipeline. Free is one episode a day. This does not debit prepaid credits. Poll get_episode with the returned id. discard_script drops the saved draft and writes a new script.

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": {
      "id": "<id>"
    },
    "name": "generate_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShow id.
discard_scriptNoSet true to drop the saved draft and write a new script. Omit it to keep a saved draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only but idempotent, non-destructive write; the description adds substantive context beyond that by explaining the once-per-delivery-day rule and the deleted-day tombstone that underpin the idempotent behavior. It also discloses billing behavior (no prepaid credit debit), which annotations cannot convey. It does not cover failure modes or whether a tombstoned day errors versus returning silently, leaving a small gap.

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

Conciseness3/5

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

Purpose is front-loaded, which is good, but the middle is cluttered: "one episode per delivery day," "the same deleted-day tombstone," and "Free is one episode a day" partly repeat each other, and "the same ... as the website" is vague to an agent that has no website context. The discard_script sentence duplicates the schema description almost verbatim.

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?

With no output schema, the description correctly tells the agent that an id is returned and how to retrieve the result via get_episode. Business rules and billing effects are covered, which matters for a mutating tool. Only the failure/error behavior for a duplicate delivery day and any permission requirements are left unstated.

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 both `id` and `discard_script` are already documented in the schema. The description restates the discard_script effect (drop the saved draft, write a new script) but adds no format, constraint, or interaction detail the schema lacks. Baseline 3 is appropriate.

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 gives a specific verb and resource ("Start today's episode for this show") and is clearly distinct from siblings like get_episode, delete_episode, or list_episodes. The trailing note about polling get_episode for the result further pins down what this tool produces versus what the read tools do.

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?

The description supplies real preconditions: one episode per delivery day, the Free-tier daily cap, the deleted-day tombstone, and the fact that prepaid credits are not debited. It also routes the agent to get_episode for polling, which is the natural next step. It stops short of explicitly stating when *not* to call it, but the constraints imply the exclusion conditions.

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