Skip to main content
Glama
Podcast MCP
by calebn

approve_edits_tool

Approve pending podcast edits by ID or in bulk and apply them to the timeline; cuts failing audio-quality, position, or unsure-word checks stay held, with audio-check override for confirmed cuts.

Instructions

Approve pending edits by id (or every pending proposal), applying them to the timeline.

To give every pending sound its own suggested action at once, use apply_suggested_actions_tool.

all_pending=true approves every pending proposal; ids approves those. Either way the edits that pass the automatic audio-quality and cut-position checks apply. ids lists the edits this call approved, and held lists the ones stopped (each with its finding) and left pending. unknown_ids lists requested ids that match no pending or approved edit (the rest still apply); the call fails with approve_unknown_ids when none of the ids match. When the user says to approve a held cut anyway, repeat with override_audio_checks=true: it skips those checks for this call and records the override (actor and surface) in History and the edit log.

More than one edit (all_pending or several ids) is a bulk approve: a cut that covers a word the transcript is unsure about (below analysis.unsure_word_confidence, 0.7 as shipped) stays pending and comes back in held with reason unsure_word. Check those words (low_confidence_words_tool), then approve that one cut by passing its single id; override_audio_checks does not apply to it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "approve_edits_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
all_pendingNo
project_pathNo
override_audio_checksNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / all_pending
      Added value: +{
      +  "default": false,
      +  "title": "All Pending",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ids"
      +}
    • removedInput schema / properties / ids_json
      Removed value: -{
      -  "title": "Ids Json",
      -  "type": "string"
      -}
    • addedInput schema / properties / override_audio_checks
      Added value: +{
      +  "default": false,
      +  "title": "Override Audio Checks",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path",
      -  "ids_json"
      -]
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses that automatic audio-quality and cut-position checks gate application, that bulk approval holds cuts over unsure words, that overrides are recorded with actor and surface in History and the edit log, and that the call fails with approve_unknown_ids when no ids match. It does not state permission or reversibility characteristics, which keeps it short of 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?

Front-loaded with the core action and the sibling alternative, then layered detail in descending importance. The parenthetical threshold '(0.7 as shipped)' and repeated restatement of the held/override rules add some length that could be trimmed.

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?

A mutation tool with no annotations and an output schema present; the description defines the returned ids/held/unknown_ids buckets anyway and explains gating and failure modes. Only the project_path parameter and any scoping assumptions about which project is affected are left unaddressed.

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 description coverage is 0%, so the description must compensate; it gives real meaning to ids, all_pending, and override_audio_checks, including the interaction between override and unsure-word holds. project_path is never mentioned, leaving one of four parameters unexplained.

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?

States a specific verb and resource ('Approve pending edits by id ... applying them to the timeline') and also covers the all-pending variant, which cleanly separates it from apply_suggested_actions_tool and reject_edits_tool.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use apply_suggested_actions_tool when every pending sound needs its own suggested action, use ids for a subset, all_pending for everything, and repeat with override_audio_checks=true only when the user insists on approving a held cut. It also states the one case where override does not apply (unsure_word).

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

Deploy Server

Other Tools