Blaze

Set design text

set_design_text

DestructiveIdempotent

Replace the words of one text element in an existing design. The element keeps its font, size, color, and position; the text re-wraps to fit its box. Use it to change a headline, caption, or button label. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview.

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": {
      "workspace_key": "<workspace_key>",
      "design_id": "<design_id>",
      "element": "<element>",
      "text": "<text>"
    },
    "name": "set_design_text"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The new text.
`element`	Yes	The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:...").
`design_id`	Yes	The design id (from compose_design or generate_post) or the key from a /designs/<key> URL.
`workspace_key`	Yes	Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotent=true, and the description usefully clarifies what that means: the words are replaced but font, size, color and position are preserved and text re-wraps to its box, with the change persisted. It also discloses the return payload (updated design structure plus rendered preview), which matters since no output schema exists; it does not address reversibility or permissions beyond the workspace_key parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action, then behavior, then return value. No filler or repetition of the title.

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?

A destructive mutation with no output schema is well covered: it explains preservation of styling, persistence, and the response shape. Minor gap: it doesn't say what happens if a non-text alias (e.g. "image-1") is passed, even though the schema lists image aliases.

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 100%, so the schema fully documents element aliases, design_id, workspace_key and text. The description adds only indirect meaning (element is a text element whose box the text re-wraps into) and no format or edge-case guidance beyond the schema, so baseline 3 applies.

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 words of one text element in an existing design") and constrains scope to a single element of an existing design, which cleanly separates it from add_design_text and set_design_text_panel. The examples (headline, caption, button label) reinforce intent.

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?

"Use it to change a headline, caption, or button label" gives a clear when-to-use context tied to editing existing text. No explicit exclusions or named alternatives (e.g. vs. add_design_text or set_design_text_panel), so it stops short of full routing guidance.

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

All Blaze tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.