Skip to main content
Glama
Podcast MCP
by calebn

list_session_takes_tool

List the takes in a staged podcast session for a take switcher to compare duration, transcript snippets, chosen/default status, and selectability before selecting or accepting a take.

Instructions

List the takes of a staged session for a take switcher (reads only).

Per take: take_index, duration_s (and per track), word_count and speech_text (a snippet; null for a take nobody has transcribed), chosen (the one select_session_take_tool picked), default (the one accept_session_suggestion_tool places when no take_index is given) and refusal ({code, message}) when accepting that take would be refused. selectable is false for an insert (its takes play in order), a session that is not pending and a replace with one take.

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

Input Schema

NameRequiredDescriptionDefault
project_pathNo
suggestion_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.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 well: it declares read-only behavior in text, documents the refusal object that signals an accept would fail, and explains the three concrete conditions under which 'selectable' is false (insert, non-pending session, single-take replace). It does not cover permissions, pagination, or what happens with an unknown suggestion_id.

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 opening sentence front-loads purpose and scope, and the per-take field inventory is dense but every listed field (take_index, duration_s, word_count, chosen, default, refusal, selectable) earns its place. The final 'selectable is false for...' sentence is a run-on that would read better as a short list, but there is little genuine padding.

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 read-only two-parameter tool with an output schema, the definition covers the semantics that the output schema cannot (meaning of chosen/default/refusal and the selectable gating rules), which is the high-value content. The remaining gap is the unaddressed input parameters and the absence of any error behavior, which keeps it below a 5.

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 0% across two parameters, so the description must compensate and does not: neither 'suggestion_id' (the required key) nor the optional 'project_path' is mentioned at all. The agent gets no guidance on what a suggestion_id refers to, where to obtain it, or when project_path matters.

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 ('List the takes of a staged session') plus a scope qualifier ('for a take switcher') and a safety note ('reads only'). It is easy to distinguish from select_session_take_tool and accept_session_suggestion_tool, which are named only as consumers of the returned flags rather than as alternatives, so the sibling routing is implicit rather than spelled out.

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?

Usage is implied: the description explains that 'chosen' is what select_session_take_tool picked and 'default' is what accept_session_suggestion_tool would place, which hints this is a pre-selection reconnaissance call. However, it never says 'call this before selecting/accepting a take' or when not to call it, so the agent must infer the workflow from field semantics.

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