Blaze

Add design text

add_design_text

Add a new text element to one slide of an existing design. Place it with x/y/width/height in design pixels, and set its typography with font_family, font_size, font_weight, and color (take the brand fonts and colors from get_brand_kit). Optionally give it a panel behind it, such as a button. Existing elements are not changed. 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>",
      "slide": "<slide>",
      "text": "<text>"
    },
    "name": "add_design_text"
  }
}

Input Schema

Name	Required	Description
`x`	No	Left edge, in design pixels.
`y`	No	Top edge, in design pixels.
`text`	Yes	The words to add.
`color`	No	Text color: a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency); take brand colors as hex values from get_brand_kit. Defaults to black.
`panel`	No	Optional panel behind the text: { "color": a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency); take brand colors as hex values from get_brand_kit, "opacity": 0..1, "shape": "box"\|"silhouetteRounded"\|"callToAction" }.
`slide`	Yes	The slide to add to: "frame" for a single design, or the slide alias ("s1", "s2", ...) from the design structure.
`width`	No	Box width, in design pixels.
`height`	No	Box height, in design pixels.
`design_id`	Yes	The design id (from compose_design or generate_post) or the key from a /designs/<key> URL.
`font_size`	No	Size in points. Defaults to 48.
`font_family`	No	Font family. Defaults to Inter.
`font_weight`	No	Weight, e.g. 400 or 700. Defaults to 400.
`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.4/5.0

Behavior4/5

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

Annotations already declare the non-readonly, non-destructive, non-idempotent profile, so the bar is lower. The description adds real value beyond them: existing elements are untouched, the change is persisted, and the response includes the updated structure plus a rendered preview.

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 action and placement, then typography, then optional panel, then side effects and return. Every sentence carries information; only the panel clause is a touch dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 13 parameters including a nested panel object and no output schema, the description still explains placement units, typography defaults via brand kit, the optional panel, mutation semantics, and the shape of the response. Nothing an agent needs to call it correctly is missing.

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 baseline is 3. The description adds cross-tool meaning by tying font_family/font_size/font_weight/color to get_brand_kit and summarizing the geometry and optional panel, going slightly beyond the per-parameter docs.

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 ('Add a new text element to one slide of an existing design') and is clearly separable from siblings like add_design_logo, add_design_shape, and set_design_text. An agent can tell what is being created and where 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 Guidelines4/5

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

Gives clear context: it operates on an existing design, targets a specific slide, and directs the agent to get_brand_kit for fonts and colors. The line 'Existing elements are not changed' implicitly routes edits to set_design_text, but no explicit when-not or alternative is named.

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.