Skip to main content
Glama

var2_read_motion_graphics

Read-only

Free, owner-only. Read the current motion piece before editing. Start with view:"summary" for its layer IDs and revision, then layer_ids for up to four complete layers. Use typed layer_patches for small edits. The legacy default/full view returns the complete spec and can exceed model context; never save a truncated result.

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

Input Schema

NameRequiredDescriptionDefault
viewNoPrefer summary; omitted preserves the legacy full-spec response.
layer_idsNoReturn only these complete layers plus revision, without the full spec.
project_idYesThe motion piece (video project) id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful context beyond that: free/owner-only access, the context-size risk of the full view, and a warning never to save a truncated result. It does not describe exact return structure, but for a read tool with annotations this is strong supplemental disclosure.

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 free/owner-only and purpose, then gives a compact summary-to-layer_ids workflow and a full-view warning. One sentence about typed layer_patches is out of place in a read tool and slightly disrupts the otherwise efficient structure.

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?

No output schema exists, so the description must explain returns; it identifies revision, layer IDs, complete layers, and the risk of the full spec. That is complete enough for correct invocation, though it does not detail the structure of returned layer objects.

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; the description adds operational meaning by explaining that summary yields layer IDs and revision, layer_ids returns complete layers plus revision, and omitted/full is the legacy complete-spec response with context risk. That adds value beyond the schema descriptions, though the mention of layer_patches is not a parameter of this tool.

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?

States a specific verb and resource: read the current motion piece, with scoped summary/layer views. The read-before-edit framing separates it from mutation siblings, though it never explicitly names var2_update_motion_graphics or var2_save_motion_graphics.

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 says to start with view=summary, then request up to four layer_ids, and warns that the legacy full view can exceed context and truncated results must not be saved. It gives clear view-selection guidance but does not route edits to a named sibling tool, instead mentioning 'typed layer_patches' without naming the 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