Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Set design text panel

set_design_text_panel
DestructiveIdempotent

Add, restyle, or remove the filled panel behind one text element in an existing design, such as a button or a strip that makes text readable over a photo. Pass panel { "shape": "none" } to remove it. 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>",
      "panel": "<panel>"
    },
    "name": "set_design_text_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
panelYesThe panel: { "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"|"none" }.
elementYesThe 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_idYesThe design id (from compose_design or generate_post) or the key from a /designs/<key> URL.
workspace_keyYesKey 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.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower; the description still adds real context by disclosing that removal is achieved via shape=none and that the change is persisted to the design. It also previews the response shape (structure plus rendered preview) rather than leaving the mutation's effect opaque.

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?

The verb set is front-loaded, and the removal instruction is placed early where an agent will catch it. Three sentences with little waste, though the response sentence could be trimmed without loss.

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?

No output schema exists, and the description compensates by describing the return payload (updated design structure with aliases/positions plus a rendered preview). Combined with annotation coverage of the safety profile and fully documented params, an agent has everything needed to call it correctly.

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, but the description adds semantics the schema does not state explicitly: that shape=none is the removal switch rather than a drawing mode, and that the panel sits behind a single text element. Color/opacity details are correctly left to the schema.

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 set (add, restyle, remove) applied to a specific resource (the filled panel behind one text element), with a concrete example (button, legibility strip over a photo) that disambiguates it from set_design_text and set_design_background.

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 usage context (making text readable over an image) and an explicit terminal case: pass panel { "shape": "none" } to remove. It does not name which sibling to use instead when the intent is text-only or background change, so alternatives remain inferred.

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

All Blaze toolsInspect
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.

Resources