Skip to main content
Glama

PostPod

Delete episode

delete_episode
DestructiveIdempotent

Delete one daily episode the same way the website Library does. The row stays as a tombstone, the script is cleared, and the audio file is removed. That delivery day is not generated again, except for the website's admin reopen of the same row. An episode that is not this account's returns the same not-found result as a missing id. Deleting it again is success. This does not debit prepaid credits.

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": "delete_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEpisode id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

On top of annotations that already flag destructive and idempotent, the description spells out the exact consequences: the row survives as a tombstone, the script is cleared, the audio file is removed, and the delivery day is not regenerated. It also discloses not-found behavior for foreign accounts, idempotent re-deletion, and that no prepaid credits are debited.

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?

Five short sentences, all front-loaded with the core action and consequence, and each one adds a distinct fact. The phrase "the same way the website Library does" is idiomatic rather than precise, but it is still useful.

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?

There is no output schema and only one parameter, so the description needs to carry the behavioral weight, and it does: irreversibility, the one exception (admin reopen), idempotency, privacy or scoping behavior, and the billing side effect are all covered.

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% with one documented parameter, so the baseline is already met. The description adds meaning beyond that schema by saying an episode belonging to another account "returns the same not-found result as a missing id", which tells the agent how id errors are surfaced.

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 names a specific verb and resource ("Delete one daily episode") and adds scope ("one daily episode the same way the website Library does"), so an agent can tell it apart from get_episode/generate_episode 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 clearly establishes the deletion context and states one exclusion ("except for the website's admin reopen of the same row"), but it never tells the agent when deletion is the right move rather than, say, verifying with get_episode first, or which sibling to reach for instead.

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