Skip to main content
Glama

cinematic_ads_undo_fix

DestructiveIdempotent

Undo one fix of a moment (an id from production.fixes): that moment goes back to how it was. Build the final video again with cinematic_ads_export to get a file without it. Free.

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": {
      "project_id": "<project_id>",
      "fix_id": "<fix_id>"
    },
    "name": "cinematic_ads_undo_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
fix_idYesThe fix's id from production.fixes in cinematic_ads_get_project.
project_idYesProject id from cinematic_ads_list_projects or cinematic_ads_create_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the meaningful consequence (the moment returns to its prior state) and the required follow-up export step, plus a 'Free' cost note. It does not cover permissions or rate limits, but the state-change effect is well disclosed.

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?

Three tight sentences, front-loaded with the action and effect, then the follow-up step and cost note. No filler.

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 two-parameter mutation with full schema coverage and no output schema, the description covers effect, follow-up, and cost. Only permissions/error behavior is left implicit.

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 100%, so both fix_id and project_id are already documented with their sources; the description's mention of 'an id from production.fixes' restates the schema rather than adding format or lookup detail.

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?

Names a specific verb (undo) plus the resource (one fix of a moment) and clarifies the resulting state ('that moment goes back to how it was'). It is clearly distinguishable from cinematic_ads_fix_moment, its natural counterpart.

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?

States the use case and tells the agent to run cinematic_ads_export afterward to rebuild the final video without the fix. It lacks an explicit 'when not to use' or a named alternative for reverting in bulk, so it falls just short of a 5.

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