Skip to main content
Glama
Podcast MCP
by calebn

accept_session_suggestion_tool

Accept a pending session suggestion to insert or replace it on the multitrack timeline, validating anchors and takes while keeping the change undoable.

Instructions

Place a pending session on the timeline (one undo step, "Added Session N").

An insert opens the session's length at its insert point on every dialogue track and places its takes, room-tone beds and live comments there. A replace removes its range on every dialogue track and puts one take in its place (take_index, else the selected or last take) and discards the other takes' staged segments and the live comments held on them (the result's discarded_takes, comments_not_placed and discard_message say what; one Undo brings them back; the recordings stay in the project). Its range is found again from the audio it was staged on. Refuses a session that is not pending, a range or insert point that is gone or changed (stale_anchor), an unknown take (take_not_found), a take_index on an insert (take_not_applicable), a track the take did not record (track_not_recorded) and pending edits inside the range (pending_edits_in_range). A replace that also removes another track's speech stays unchanged and returns needs_confirmation until you repeat with override_audio_checks=true (recorded). The result lists non-dialogue tracks that did not move (unmoved_track_ids).

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": {
      "suggestion_id": "<suggestion_id>"
    },
    "name": "accept_session_suggestion_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
take_indexNo
project_pathNo
suggestion_idYes
override_audio_checksNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses that this is a single undo step ('Added Session N'), exactly what a replace discards, that Undo restores it and the recordings remain in the project, and enumerates the stale_anchor, take_not_found, take_not_applicable, track_not_recorded and pending_edits_in_range refusals.

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, then the insert/replace effects, then the refusal list, then the override flow. The parenthetical asides and the multi-clause refusal sentence make it dense, but almost every clause carries operational information rather than filler.

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?

For a four-parameter mutation with no annotations, the description covers outcomes, side effects, reversibility, error codes and the confirmation loop, and even interprets result fields despite an output schema existing. The only real shortfall is the undocumented project_path parameter, plus no pagination- or size-relevant caveat, which is minor here.

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 0%, so the description must compensate and it does for take_index (fallback to the selected or last take, rejected on an insert) and override_audio_checks (the confirmation retry flag). suggestion_id is only implied, and project_path is never mentioned, leaving one of four parameters without any meaning beyond its name.

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?

States a specific verb and resource ('Place a pending session on the timeline') and immediately splits the two behaviors, insert vs replace, down to what each does to dialogue tracks, takes, room tone and comments. It does not explicitly name the sibling that rejects a suggestion (skip_session_suggestion_tool), so the differentiation is implied by the word 'pending' rather than stated.

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?

Gives strong precondition guidance: it refuses a session that is not pending, a stale anchor, a range with pending edits, and explains that a replace removing other tracks' speech returns needs_confirmation until repeated with override_audio_checks=true. Missing is an explicit statement of when to choose this over the sibling that auditions or skips a suggestion.

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