Skip to main content
Glama

var2_update_motion_graphics

Free, owner-only. Prefer bounded layer_patches plus expected_updated_at from a fresh summary read: edits exact copy, solid colors and fonts while preserving all untouched data. Revision conflicts require re-reading. Legacy full spec replacement remains available only when you have the complete current spec. Never reconstruct a truncated spec.

Input Schema

NameRequiredDescriptionDefault
nameNo
specNoThe full edited Motion Spec.
project_idYes
layer_patchesNo
expected_updated_atNoRequired for layer_patches: exact updated_at returned by the latest read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the full load, and it delivers real context: cost ('Free'), permission model ('owner-only'), conflict behavior ('Revision conflicts require re-reading'), and a preservation guarantee ('preserving all untouched data'). It omits what an error on a stale expected_updated_at looks like and whether a name-only update is permitted, which for a mutation tool with zero annotation coverage leaves some risk unexplained.

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?

Front-loads the two constraints an agent must know first ('Free, owner-only') and packs the mode selection, conflict rule, and fallback warning into four sentences with no filler. The telegraphic phrasing is dense but each clause carries a distinct instruction.

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-mode oneOf schema with nested patch objects, no output schema, and 40% parameter coverage, the description covers the decision logic, permission, cost, and conflict handling an agent needs before calling. Remaining gaps are the undocumented name parameter and the absence of any statement about what a successful update returns.

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 40%, so the description must compensate, and it partially does: expected_updated_at is explained as coming from 'a fresh summary read', layer_patches is characterized as 'bounded' (hinting the maxItems 8 limit), and spec is framed as a complete current spec. The name parameter is never mentioned in the description or schema, so a rename-only edit is undocumented, and no field-level meaning is added beyond what the schema already states.

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 conveys an update operation on an existing motion-graphics project and distinguishes two modes: bounded layer_patches editing versus legacy full spec replacement. It never names a sibling tool, so the agent must infer routing from the read/save/preview naming pattern rather than being told explicitly.

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 states the preferred path (layer_patches plus expected_updated_at from a fresh summary read) and the exclusion for the fallback ('only when you have the complete current spec', 'Never reconstruct a truncated spec'). No guidance on when to use this versus var2_save_motion_graphics or var2_preview_motion_graphics, which are the real routing ambiguities.

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