Skip to main content
Glama

Update a Playground text node

playground_canvas_update_text
DestructiveIdempotent

Replace the editable text content of an existing text node. Requires project edit access, the node ID and the current expectedRevision from canvas_read. Reuse idempotencyKey only for an identical retry. On revision_conflict, read the canvas and rebuild the change. Returns the node ID, updated canvas revision and replay status.

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>",
      "nodeId": "<nodeId>",
      "text": "<text>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_canvas_update_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesEditable text to save in the selected text node or workflow input.
nodeIdYesExisting canvas node ID returned by canvas_read, node search or creation.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
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
nodeIdYes
replayedYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotentHint=true, but the description adds real operational context beyond them: the edit-access requirement, the conflict-recovery loop (re-read canvas and rebuild), and the retry semantics for idempotencyKey. It does not spell out that the prior text value is lost with no undo, which is the main remaining behavioral fact for a destructive write.

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?

Four dense, front-loaded sentences that lead with the action and then cover prerequisites, retry rules, and failure recovery. The final sentence about return values is largely redundant given an output schema exists, but it costs little.

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 destructive, permission-gated mutation with a complete schema, full annotations, and an output schema, the description covers auth, input sourcing, conflict recovery, and idempotency. The gap is that it never explains what a 'text node' is relative to other node types or what happens to the previous text.

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 100%, so all five parameters are already documented in the input schema, including expectedRevision's conflict behavior and idempotencyKey's reuse rule. The description largely restates those points and adds no new parameter-level meaning, making 3 the correct baseline.

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: 'Replace the editable text content of an existing text node.' The word 'existing' plus 'replace' implicitly separates it from playground_canvas_add_text (new node) and playground_canvas_update_node_layout (layout, not content), so an agent can pick the right one without opening a schema.

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 prerequisites (project edit access, node ID, current expectedRevision from canvas_read) and an explicit recovery path for revision_conflict, plus a rule for when to reuse idempotencyKey. It stops short of naming alternatives such as add_text for brand-new nodes, so the when-not case is left to inference.

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.