Skip to main content
Glama

katto_add_hook

Add bold text over a clip's opening seconds to stop the scroll and re-render it. Pass your own hook or let AI write one, then poll for the new clip URL.

Instructions

Add a hook, big bold text over the first seconds that stops the scroll, to one finished clip and re-render it. Pass text to use your own (max 80 characters, 3-7 words reads best) or omit it and Katto's AI writes one from the clip in its language. position: top (default) or center; duration: 1-10 s (default 4). Styled like the editor's AI Hook (white, boxed, pop-in). Does NOT use video quota; the original clip is kept. Not idempotent: each call starts a new render, and a re-render starts from the original clip, so calling it again replaces the hook rather than stacking two. Returns { rerender_id, hook_text, generated, status_url }; poll katto_get_rerender for the new clip_url.

Input Schema

NameRequiredDescriptionDefault
idYesJob id.
textNoThe hook to display (max 80 characters; 3-7 words reads best). Omit to let Katto write one from the clip.
durationNoHow many seconds the hook stays on screen, 1-10 (default 4).
positionNoWhere the hook sits on the frame (default top).
clip_indexYes0-based clip index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only give readOnly/idempotent/destructive/openWorld flags): adds that video quota is not consumed, the original clip is preserved, why it is non-idempotent, the replace-not-stack consequence, the visual style applied, and the exact return shape. This is unusually rich 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.

Conciseness4/5

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

Front-loaded with the core action before the parameter and behavior detail, and every sentence carries information. It is fairly dense and slightly long, but no sentence is filler.

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?

With no output schema, the description compensates by describing the return object ({ rerender_id, hook_text, generated, status_url }) and the follow-up poll via katto_get_rerender. Combined with quota, non-idempotency and clip-preservation notes, an agent has everything needed to call and follow up correctly.

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 100%, so the baseline is 3, but the description adds interpretive meaning: it stresses the text/omit branch that selects AI generation, gives the readability heuristic (3-7 words), and notes the default position and duration. It largely restates schema defaults, which caps it below a 5.

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?

States a specific verb and resource ('Add a hook ... to one finished clip and re-render it') and immediately characterizes the artifact ('big bold text over the first seconds that stops the scroll'). This is clearly distinguishable from siblings like katto_retitle_clip, katto_adjust_clip and katto_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?

Explains the two usage modes (supply your own text vs omit for AI-generated) and warns that repeat calls replace rather than stack the hook. It also flags that no video quota is consumed. It stops short of naming an alternative sibling or stating when-not-to-use, so it is clear context rather than full routing guidance.

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