Skip to main content
Glama

Get a video ready to post

touch_up

Opens one of the connected account's finished videos in Cirrela's "Ready to post" panel: word-by-word captions, music, a voice-over, a new format (9:16, 1:1, 16:9) or a sharper version. Returns the link; the panel shows the exact cost in credits before the click, and the original stays. Needs the person's Cirrela account.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe video's id, from create_video or get_generation.
kindNoOptional: which touch-up the person wants.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare this is not read-only and not destructive; the description adds genuinely new behavioral facts — the original is preserved, a link is returned, and the cost is previewed before committing. However, it does not address the non-idempotent hint: repeat invocations would presumably create and charge for additional renders, and that risk is never stated.

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?

The purpose is front-loaded in the first clause, and the enumerated options are compact. The second sentence is dense, packing return value, cost preview, original preservation, and account requirement into one line, but every clause carries distinct information.

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?

For a mutating tool with no output schema, the description covers the essentials: what is produced, that a link comes back, that the source is untouched, and the credit-cost gate. The remaining gap is the omitted-kind default and the cost/duplication implication of calling repeatedly.

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 would be 3, but the description adds real meaning: it explains what each enum value actually does (word-by-word captions, a new format with 9:16/1:1/16:9, a sharper version) and clarifies that the kind is optional. It does not explain the behavior when kind is omitted (whether the panel simply opens with all options).

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 gives a concrete verb and resource — opens a finished video in Cirrela's 'Ready to post' panel — and enumerates the specific touch-ups available (captions, music, voice-over, reframe, upscale). It also implicitly separates itself from create_video and get_generation by operating on an already-finished video rather than producing a new one.

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 establishes the preconditions clearly: the video must be finished and the person needs a Cirrela account, and it notes the exact credit cost is shown before the click, so an agent need not route to estimate_cost first. What is missing is an explicit statement of when NOT to use this or which sibling to prefer when no finished video exists yet.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources