Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Recolor design element

recolor_design_element
DestructiveIdempotent

Change the color of one element in an existing design. On a text element it sets the text color. On a shape or a slide background it sets the fill: a solid color, or a gradient. Pass color for a solid color or gradient for a gradient. 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>"
    },
    "name": "recolor_design_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoThe new color: a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency) or a brand color token from get_brand_kit such as "primary".
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:...").
gradientNoShapes and backgrounds only: a gradient fill, { "gradient": ["#RRGGBB", ...], "angle": <degrees> }.
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.1/5.0
Behavior4/5

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

The annotations already declare the mutation, destructive, idempotent, and non-open-world traits. The description adds useful behavioral context: the change is saved to the design, and the response includes updated design structure plus a rendered preview. It does not describe permissions or failure behavior, but it adds meaningful information beyond the annotations.

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?

The description is front-loaded with the core action and then explains element-specific behavior, argument selection, persistence, and response. Every sentence contributes useful information without repetition.

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 mutation with five parameters and no output schema, the description is fairly complete: it covers element types, color versus gradient usage, persistence, and return contents. It leaves out edge cases such as unsupported element types or permission requirements, but the essential invocation context is present.

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 description coverage is 100%, so the schema already documents all parameters. The description adds a useful selection rule: use color for solid fills and gradient for gradients, with gradient limited to shapes and backgrounds. That goes slightly beyond the schema, though it does not add much more parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: changing the color of one element in an existing design. It also clarifies how text elements differ from shape/background elements. It does not explicitly differentiate itself from nearby siblings like set_design_background or set_design_text, so it stops short of a 5.

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?

It clearly states the context for use: text elements get text color, while shapes and slide backgrounds get a fill. It also says to pass color for a solid color or gradient for a gradient. There are no explicit when-not-use rules or named alternatives, but the conditional usage context is clear.

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