Skip to main content
Glama

modify_clip

Adjust suggested clips before export by changing timing, title, or caption style. Delete unwanted clips entirely using clip number.

Instructions

Adjust a suggested clip before exporting. Change timing, title, or caption style. Use action='delete' to remove a clip entirely. Reference clips by clip_number (from get_ui_state).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexNo0-based index (deprecated, use clip_number)
actionNoAction: 'update' (default) or 'delete'update
clip_idNoUUID of the clip (alternative to clip_number)
updatesNoPartial fields to update on the clip (ignored when action='delete')
clip_numberNoClip number (1-based, from get_ui_state)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv2.7.3
    • addedInput schema / properties / updates / properties / context_line
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / updates / properties / payoff
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / updates / properties / standalone
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv2.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / updates / additionalProperties
      Removed value: -false
  3. First observedv2.0.0

TDQS

D1/5.0
Behavior1/5

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

No annotations and no description; behavioral transparency absent.

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

Conciseness1/5

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

No description to evaluate for conciseness or structure.

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

Completeness1/5

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

Tool context is incomplete; essential elements are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema parameters exist but no description to enrich their meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

No description provided; cannot determine purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No description provided; no usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nmbrthirteen/podcli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server