Skip to main content
Glama

Update Video Keys

update_video_keys
DestructiveIdempotent

Update only the metadata of a video (found by video_id or video_uuid: title, description, language as a name such as english or turkish, keywords) for the caller's merchant; any other key is refused and nothing is written. The timeline, output and render queue are changed with render_video.

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": {
      "updates": "<updates>"
    },
    "name": "update_video_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYes
video_idNo
video_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive, idempotent and non-read-only behavior, but the description adds real context beyond them: writes are all-or-nothing ('any other key is refused and nothing is written') and updates are scoped to the caller's merchant. It stops short of describing the response body or what happens on partial/unknown-key failures beyond refusal.

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?

Two sentences, no filler: the scope and refusal rule come first, the disambiguation from render_video second. The parenthetical field list is dense but every element earns its place.

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 mutation tool with no output schema and an untyped nested payload, the description supplies the allowed-key contract, the refusal semantics, the merchant scoping and the sibling alternative. The remaining gap is identification rules for video_id vs video_uuid and any return-value expectation.

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 coverage is 0% and the 'updates' object is an opaque additionalProperties bag, so the description has to carry the burden. It does list the accepted keys (title, description, language, keywords) and clarifies the language value format, but it does not state that video_id or video_uuid must be provided or how they interact, leaving half the parameter space implicit.

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 ('Update only the metadata of a video') and immediately enumerates the mutable fields plus the lookup keys. It also distinguishes itself from render_video, which handles the timeline, output and render queue, so an agent can tell the two apart without reading either schema.

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?

Explicitly names the alternative tool and the condition that selects it ('The timeline, output and render queue are changed with render_video'), which is a genuine when-not rule. It does not cover prerequisites such as whether the caller must own the video or what to do if neither video_id nor video_uuid is supplied.

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.