Skip to main content
Glama
Podcast MCP
by calebn

list_clips_tool

Lists podcast clips in timeline order for a selected track or all tracks, with optional timing steps to account for timing corrections and accurate clip lengths.

Instructions

List clips in timeline order for one track or all tracks when track_id is omitted.

A clip with timing_steps has timing corrections, so its timeline length is not source_end - source_start; include_timing_steps adds the step list.

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

Input Schema

NameRequiredDescriptionDefault
track_idNo
project_pathNo
include_timing_stepsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / include_timing_steps
      Added value: +{
      +  "default": false,
      +  "title": "Include Timing Steps",
      +  "type": "boolean"
      +}
  2. Changed4 schema fields changedv0.1.1
    • 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"
      -]
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose non-obvious domain behavior — that a clip with timing_steps has a timeline length different from source_end - source_start — which is valuable. It never states the operation is read-only, whether results are paginated, or what ordering/scope constraints apply across projects, so a listing tool with zero annotation coverage is left partly opaque.

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?

Two short sentences with the primary scope statement front-loaded; nothing is filler. The hard line wrapping is an artifact rather than a structure choice, but the content order is correct.

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?

An output schema exists, so return values need not be described, and this is a low-risk read operation with no required parameters. The only meaningful omission is any explanation of project_path, which matters for a tool that can span tracks or projects.

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 description coverage is 0%, so the description must compensate. It does explain the default semantics of an omitted track_id (all tracks) and what include_timing_steps adds (the step list), covering two of three parameters. project_path is never mentioned, leaving a third of the parameters undocumented anywhere.

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 gives a specific verb and resource ('List clips') plus the ordering guarantee ('timeline order') and the scope rule for tracks. It does not differentiate itself from look-alike siblings such as list_social_clips_tool, so an agent must infer that distinction from the other tool's name rather than this definition.

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 the selection rule for its own parameter ('for one track or all tracks when track_id is omitted'), which is genuinely useful usage context. However it offers no when-to-use versus alternatives guidance and no exclusions, so the agent must decide on its own whether this is the right listing tool.

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