Skip to main content
Glama

Change a graphic

update_graphic

Changes a long video's graphic: its data, placement or words (at, until, beats; null resets until or beats to the default), with the same checks as add_graphic. Renders it again when what it shows changes, or when its last render failed. Returns the same as add_graphic.

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

Input Schema

NameRequiredDescriptionDefault
atNoThe word it starts on, as { take_id, word } with the word's index from get_transcript
dataNoThe template's data, matching its data_schema in list_graphics
beatsNoOne word per step (a worked sum's lines or a timeline's markers), in order: each step appears as its word is said. null for the template's own timing
untilNoThe word it ends on; null for its build plus 2 s, at least 5 s (30 s at most)
placementNofull replaces the picture; right, left and band are overlays (each template lists the ones it takes)
graphic_idYesFrom add_graphic or get_project
project_idYesFrom create_project
check_againstNoA scene id (its script, else its take's transcript) or the script's text: every figure in the data must appear in it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations only declaring the mutation profile (readOnly=false, destructive=false, idempotent=false), the description adds real behavioral context: it re-renders when displayed content changes or when the last render failed, and null values reset timings to defaults. Remaining gaps are that authorization requirements and partial-merge vs replace semantics on 'data' are unstated, and the return value is deferred to add_graphic.

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?

Two dense sentences with the mutation surface front-loaded before the re-render side effect and reset semantics; nothing is filler. The final clause "Returns the same as add_graphic" is efficient given no output schema, though it silently requires knowledge of a sibling's contract.

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 an 8-parameter mutation tool with nested objects and no output schema, the description covers the timing/placement/data facets and the render side effect but never addresses check_against, ordering/validation limits (beats maxItems 5), or whether omitted fields are preserved or cleared on an update. An agent must consult the schema and infer the update-merge contract.

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, and the description earns above baseline by defining reset semantics for until/beats that the schema does not state (the schema only describes the null default, not that it is a reset) and by naming the modifiable facets. check_against and its figure-validation constraint are left entirely to the schema, which keeps it from a 5.

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?

"Changes a long video's graphic: its data, placement or words" gives a specific verb, resource, and the exact facets that can be modified, and the contrast with add_graphic is implied by "changes" plus "the same checks as add_graphic." It stops short of an explicit "use add_graphic to create, this to modify" routing statement, so it is clear but not fully sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: operate on an existing graphic, and pass null to reset until or beats to defaults (a genuinely useful when-to guideline). However, no alternative is named explicitly — preview_graphic is never mentioned as the thing to call first, and there is no statement about when not to use this tool.

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