Skip to main content
Glama

Edit the Playground canvas in one batch

playground_canvas_apply_operations
DestructiveIdempotent

Apply one atomic, revision-checked, idempotent batch of non-paid canvas edits: create_node (text, image, video, video-stitch, comment, image-compare, output-gallery, video-frame-grab, list-node), update_node, connect, disconnect, group, ungroup, delete and tidy. Refer to nodes created earlier in the batch as "$name". Nodes without a position are placed in free space beside what feeds them. Connections use the same handle rules as the browser; image → video accepts role first_frame, last_frame or reference; image-compare takes two images, output-gallery collects images, and video-frame-grab takes one clip (framePosition first or last). A list-node takes items (text, one per run); connect it to an image node and that node runs once per item when generated (set batchCombineMode cross or zip on the image node for two lists). The batch commits as one reversible revision, or nothing changes. It never starts generation. Returns the mutation receipt, updated revision and created or changed canvas references.

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": {
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>",
      "operations": "<operations>"
    },
    "name": "playground_canvas_apply_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
operationsYes
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
createdYes
summaryYesHuman-readable summary of the applied canvas operations.
replayedYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare idempotentHint and destructiveHint, and the description adds meaningful context: revision-checked commit, all-or-nothing semantics, idempotency key retry rules, and that nothing is generated. However the annotations already carry the safety profile, so the marginal gain is moderate rather than decisive.

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?

Dense but front-loaded: the operation list comes first, then reference syntax, placement rules, and connection semantics. Some node-type enumeration duplicates the schema enum, but no sentence is pure 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?

Covers atomicity, revision checking, idempotency, and returns ("mutation receipt, updated revision and created or changed canvas references"). With an output schema present the return-format detail is not strictly needed, and the definition is otherwise complete for a multi-operation mutation tool.

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 75%, so most parameters are documented structurally, and the description mostly restates aspects of the same batch semantics (node placement, image roles, list-node items). Its additional value over the schema is limited to the overall atomicity framing rather than per-parameter 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?

Opens with a specific verb+resource ("Apply ... batch of canvas edits") and enumerates every supported operation (create_node, update_node, connect, disconnect, group, ungroup, delete, tidy). The phrase "in one batch" plus the enumerated node types clearly separates it from single-node siblings such as canvas_add_text and canvas_update_text.

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?

Gives strong context: use when multiple canvas edits must land atomically, and explicitly states "It never starts generation," steering the agent to generation tools for that purpose. It does not name a specific alternative for one-off edits, so the when-not-to-use side is only implied.

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.