Skip to main content
Glama

ampache_podcasts

Destructive

Manage podcasts and episodes: list, retrieve, create, edit, delete, and update feeds. Writes require confirm=true and AMPACHE_ALLOW_WRITES=true; lists support offset and limit pagination.

Instructions

Podcasts and episodes: list, get, create, edit, delete, and feed update. Writes run only when confirm is true and AMPACHE_ALLOW_WRITES=true. List actions default to offset 0 and limit 25 (max 500). Actions: podcast, podcast_create, podcast_delete, podcast_edit, podcast_episode, podcast_episode_delete, podcast_episodes, podcast_update, podcasts, update_podcast.

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": {
      "action": "<action>"
    },
    "name": "ampache_podcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNo
urlNo
condNo
feedNo
sortNo
syncNo
exactNo
limitNo
titleNo
actionYesAmpache operation to call.
filterNo
offsetNo
updateNo
catalogNo
confirmNoBoolean true runs the write when AMPACHE_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
includeNo
websiteNo
copyrightNo
generatorNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and openWorldHint=true, and the description adds the important operational gate: writes only execute when confirm is true AND AMPACHE_ALLOW_WRITES is set, otherwise it is a preview that sends nothing. It does not identify which of the enumerated actions are the destructive ones, which would have earned a 5.

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?

Three compact, front-loaded sentences: what it covers, write-safety gating, pagination defaults, then the action list. The trailing action enumeration largely duplicates the action enum in the schema, making the last sentence partly redundant, but nothing else is wasted.

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

Completeness3/5

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

For a destructive, non-idempotent, 20-parameter tool with no output schema, the description covers the safety gate and pagination but leaves the bulk of the parameter surface and the per-action parameter requirements undocumented. An agent can tell whether a write will fire, but not which fields each action needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10% across 20 parameters; only action and confirm carry schema text. The description adds real meaning for confirm and for pagination (offset defaults to 0, limit to 25 with max 500), but the other ~17 parameters (feed, url, title, filter, catalog, include, sort, exact, sync, etc.) are left completely unmapped and unexplained.

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?

The description names the resource (podcasts and episodes) and the verb set (list, get, create, edit, delete, feed update), then enumerates the concrete action values. That is enough to distinguish it from siblings like ampache_playlists or ampache_catalogs, though it never explicitly says how it differs from them.

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?

It states a real usage precondition for writes (confirm=true plus AMPACHE_ALLOW_WRITES=true) and the dry-run behavior otherwise, which is genuinely useful. It gives no guidance on choosing among the ten actions or on when a caller should prefer another tool, so routing is only implied by action names.

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