Skip to main content
Glama

Update layer

update_layer

Set layer properties such as position, scale, opacity, visibility, or timeline window on an existing project layer to commit changes immediately without a planner or export.

Instructions

Deterministic edit: set registry properties on one existing layer of a project, committed immediately (no planner, no export). E.g. {"x": 540, "y": 960}, {"scale": 1.2}, {"opacity": 0.5}, {"volume": 0.3}, {"visible": false}, {"z_index": 4}, or its timeline window {"start_time": 2, "end_time": 8}. Unknown keys are ignored, and an update that changes nothing is an error (NO_CHANGE). Not for keyframed animation (use autonomous_edit), and not "text" on a caption group (refused: it would overwrite every caption). Get layer ids from get_project (project.scene.layers[].id).

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>",
      "layer_id": "<layer_id>",
      "properties": "<properties>"
    },
    "name": "update_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idYesId of the layer to change.
project_idYesProject whose committed scene is edited.
propertiesYesLayer property keys to values (non-empty).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description adds real behavior: unknown keys silently ignored, a NO_CHANGE error when nothing changes, and an explicit refusal path for caption-group text. The one gap is that it never says what the call returns or how the committed change is confirmed.

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-loaded with the core action and immediately followed by examples, exclusions and error semantics; every clause carries information. It is a single dense run-on paragraph, though, and the long example list could be tightened without losing value.

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 a mutation tool with no output schema, the definition covers refusals, no-op errors, ignored keys and id sourcing well. It stops short on return value and on whether partial failures within the properties object are possible, which leaves a small but real hole.

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, but the description adds genuine meaning by enumerating accepted property keys and value shapes ({"x": 540, "y": 960}, {"scale": 1.2}, {"start_time": 2, "end_time": 8}) and by noting unknown keys are ignored. That is information the schema's generic object type does not convey.

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 ('set registry properties on one existing layer of a project') and pins the scope with 'committed immediately (no planner, no export)'. It also distinguishes itself from autonomous_edit, so an agent can route correctly without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance: 'Not for keyframed animation (use autonomous_edit), and not "text" on a caption group (refused)'. It also states the prerequisite for obtaining layer ids ('Get layer ids from get_project').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.