Skip to main content
Glama
Podcast MCP
by calebn

segment_save_tool

Save selected podcast clips to the library as segments by clip IDs or time range, creating a new version when audio changes while leaving the episode unchanged.

Instructions

Save clips of an episode into the library as a copy (podcast segment save).

Pass clip_ids or time_range (such as 0:00-0:22), not both. kind is intro, outro, sponsor, sting or other; it is guessed from the position when omitted. The episode is not changed (a project still under its retired entry-file name is not renamed). The same name with new audio becomes the next version of that segment; identical audio is reported unchanged. Returns {status, id, version}.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
nameYes
roleNo
clip_idsNo
time_rangeNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.8/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 load and does well: it states the episode is not modified, that a reused name with new audio bumps the version, that identical audio reports 'unchanged', and that kind is auto-guessed. Remaining gaps are permissions/authentication and whether the save is atomic; those are minor for this operation.

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 purpose, then ordered constraints, defaults, side effects, and return shape — each sentence carries information. The parenthetical about a retired entry-file name is oddly specific and adds density, but it is not 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?

Given six parameters, zero schema coverage, and no annotations, the definition covers the semantics an agent needs to invoke it correctly, and the output schema means the brief '{status, id, version}' note is sufficient. Only role and project_path are left to guesswork.

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% across six parameters, so the description must compensate — and it does for the important ones: it explains clip_ids vs time_range mutual exclusivity, gives a concrete time_range format ('0:00-0:22'), and enumerates kind values (intro, outro, sponsor, sting, other) that the schema does not, since kind is typed as a bare string. role and project_path remain unexplained, which keeps it below 5.

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?

Concrete verb and resource: 'Save clips of an episode into the library as a copy,' with the underlying operation named ('podcast segment save'). It does not explicitly distinguish itself from nearby siblings such as copy_segment_tool or duplicate_segment_tool, so the agent must infer the boundary from 'save into library' versus 'copy/duplicate'.

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?

Gives a hard usage constraint ('Pass clip_ids or time_range, not both') and a defaulting rule for kind, which is real guidance. However, it never says when to reach for this tool instead of copy_segment_tool, duplicate_segment_tool or kit_save_tool, so tool-level selection is left implicit.

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