Skip to main content
Glama
Podcast MCP
by calebn

apply_suggested_actions_tool

Apply all pending podcast edit suggestions in one undo step, or revise a single sound's action with overrides. Cuts, lowers, or dismisses flagged audio while tracking held items.

Instructions

Apply every pending sound's own suggested action in one undo step.

Each tighten proposal carries a label and a suggested_action (propose_edits shows them). This applies all of them, or only ids: cut and shorten cut (a cut held by the automatic audio checks stays pending and is named in held), lower turns a laugh down while another speaker talks over it (otherwise it is left), leave dismisses the proposal and keeps the audio. overrides maps a decision id to another action for that sound. Returns applied by action, cut_over_speaker, held (ids still pending) and a summary sentence. When the user says to apply the held ones anyway, repeat with override_audio_checks=true (recorded in History and the edit log).

To change one sound after the batch (say a cut to leave) without undoing the rest, call again with revise=true and overrides={id: action} and no ids: it steps back to before the latest batch (which must still be the latest edit) and applies it again with that change, as one undo step. Otherwise it refuses with no_suggested_batch_to_revise.

Applying all pending sounds, or several ids, is a bulk apply: a cut or shorten over a word the transcript is unsure about (below analysis.unsure_word_confidence, 0.7 as shipped) stays pending and is named in held and in held_unsure; when every cut is held nothing is saved. Check those words (low_confidence_words_tool), then apply that one cut by passing its single id in ids; 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": "apply_suggested_actions_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
reviseNo
overridesNo
project_pathNo
override_audio_checksNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.8/5.0
Behavior5/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 so: it explains what each action (cut/shorten/lower/leave) does, that cuts held by audio checks stay pending and are named in held/held_unsure, that nothing is saved when every cut is held, that the override is recorded in History and the edit log, and that revise steps back only if the batch is still the latest edit.

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 core behavior and undo-step framing are front-loaded, then progressively rarer cases (held cuts, revise, unsure words) follow in separate paragraphs. It is dense and long, with some repetition of 'stays pending and is named in held', but nearly every sentence carries operational information.

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?

For a five-parameter, no-annotation mutation tool this is thorough, covering destructive/undo semantics, refusal behavior, and cross-tool follow-ups. An output schema exists, and the description still notes the shape of the return (applied by action, cut_over_speaker, held, summary) without over-explaining it.

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 0%, so the description must compensate, and it defines ids (subset selection), revise (must be used with overrides and no ids), overrides (decision id to alternative action), and override_audio_checks (bypass audio checks, logged). Only project_path is left without any semantic explanation, which is the one remaining gap.

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 ('apply every pending sound's own suggested action') plus the transactional scope ('in one undo step'), and it distinguishes itself from propose_edits by noting that propose_edits is where the labels and suggested_action are shown.

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?

It explicitly routes each situation: bulk apply by default or with ids, revise=true plus overrides with no ids to change one sound without undoing the batch, override_audio_checks=true when the user insists on held items, and low_confidence_words_tool followed by a single-id apply for unsure-word cuts. It also states the refusal condition (no_suggested_batch_to_revise) and the exclusion that override_audio_checks does not apply to unsure-word cuts.

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