Skip to main content
Glama

katto_retitle_clip

Destructive

Change a clip's title manually or let AI generate a title in the clip's language, with optional energetic, descriptive, fun, or shocking styles.

Instructions

Change a clip's title. Without 'title', Katto's AI writes a new scroll-stopping title in the clip's language (optional style: energetic, descriptive, fun, shocking); each AI regeneration uses one unit of the plan's monthly title-regeneration allowance (an error with 'limit' when it is used up). With 'title', that exact text is saved and nothing is spent. Synchronous: returns { title, clip_index, regenerated }. Does NOT use video quota.

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": {
      "id": "<id>",
      "clip_index": "<clip_index>"
    },
    "name": "katto_retitle_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id.
styleNoTone of the AI-generated title. Ignored when title is given.
titleNoSave this exact title instead of generating one (max 200 characters). Costs nothing.
clip_indexYes0-based clip index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavioral details: AI regeneration consumes one monthly title-regeneration unit, an error with 'limit' is returned when exhausted, exact-title saves cost nothing, and the tool does not consume video quota. It also states the synchronous return shape, which is valuable behavioral context.

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?

The description is dense but well structured and front-loaded: core action first, then conditional behavior, quota/error details, return shape, and a final quota clarification. Every sentence carries useful information.

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

Completeness5/5

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

Despite having no output schema, it documents the return object, covers both operational modes, explains quota/error behavior, and notes that video quota is untouched. An agent has everything needed to invoke it correctly.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds meaning beyond the schema: it clarifies the mode switch between AI generation and exact-title saving, ties 'style' to AI generation only, and explains the billing consequence of using 'title' versus omitting it.

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 opens with a specific verb and resource: 'Change a clip's title.' It then distinguishes the two modes (AI-generated title vs. exact title), which clearly separates this tool's behavior from sibling mutation tools like adjust_clip or rerender_clip.

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 strong conditional guidance: omit 'title' for AI generation, include 'title' to save exact text, and 'style' is ignored when 'title' is supplied. It also explains quota and error behavior. It does not explicitly compare against sibling tools, but the when-to-use conditions for this tool are clear.

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