Skip to main content
Glama
Sign In
podcli

podcli

by nmbrthirteen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

toggle_clip

Select or deselect a suggested clip by clip number to control which clips are included in the export.

Instructions

Select or deselect a suggested clip by clip_number. Selected clips are exported with export_selected.

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

Input Schema

NameRequiredDescriptionDefault
indexNo0-based index (deprecated, use clip_number)
clip_idNoUUID of the clip (alternative to clip_number)
selectedYestrue = select, false = deselect
clip_numberNoClip number (1-based, from get_ui_state)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

It discloses the core state change (select or deselect) and a downstream relationship (selected clips feed an export). However, with no annotations, the description carries the full burden and does not explain edge-case behavior, such as what happens if no clip identifier is provided or whether state is persisted across calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core purpose and no redundant wording. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool sits in a workflow between suggestions and export, and the schema's required field is only 'selected', so the description should clarify which identifier must be passed. It does not state what happens when no clip_number/clip_id/index is provided, and there is no return or side-effect detail, leaving meaningful ambiguity.

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?

The schema already documents all parameters with 100% coverage, so the baseline is 3. The description reinforces clip_number but adds no information about precedence between clip_number, clip_id, and deprecated index, nor about the fact that only selected is required while an identifier appears to be semantically necessary.

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 description names a specific action ('Select or deselect') on a specific resource ('suggested clip by clip_number') and states the workflow context ('Selected clips are exported with export_selected'). This makes it clearly distinguishable from sibling tools like modify_clip by focusing on selection rather than editing.

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?

It gives clear context: use this to mark suggested clips before exporting, reinforced by the reference to export_selected. It does not explicitly name exclusions or alternative tools, so it falls just short of full guidance.

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