Skip to main content
Glama

Log a finished video

log_video

Call once after handing over a finished video. Records which editor made it, its hook and look, so Cuttr can learn from how it does once it is posted.

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": {
      "slug": "<slug>"
    },
    "name": "log_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNoThe opening line or on-screen hook
slugYesThe editor's slug
styleNoThe look in a few words, e.g. bold captions, punch-ins, animated lists
titleNoWhat the video is about, a few words
run_idNoThe run_id given at the end of the editor's instructions
length_sNoLength in seconds
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that the tool records specific attributes and supports learning after posting, and the phrase 'Call once' hints at avoiding duplicate logging, but it does not state idempotency, permissions, failure behavior, or what the response contains.

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 definition is two compact sentences with no wasted wording. The call timing is front-loaded, followed by a brief explanation of what is recorded and why.

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

Completeness3/5

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

For a seven-parameter logging tool with no output schema and no annotations, the description covers purpose and timing but leaves operational details sparse. The schema fills most parameter gaps, yet the description does not address duplicate submissions, errors, or return behavior.

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?

Schema description coverage is high at 86%, so the input schema already documents most parameters. The description reinforces that slug identifies the editor and that hook and style are key recorded fields, but it does not add syntax or constraints beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource: calling after handing over a finished video to record editor, hook, and look. It clearly describes the logging purpose, though it does not explicitly differentiate this tool from siblings such as rate_video or add_video_link.

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 timing guidance: call once after handing over a finished video. This is useful context for selecting the tool, but it does not mention exclusions or name alternatives for related actions.

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