Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Replace design image

replace_design_image
DestructiveIdempotent

Swap the picture in one image element of an existing design for another image, keeping the element's size and position. The image URL must be publicly reachable, for example a result from search_media or get_generated_image. 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>",
      "image_url": "<image_url>"
    },
    "name": "replace_design_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
image_urlYesURL of the new image.
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.3/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and openWorld=true. The description adds materially: the mutation is persisted ('The change is saved to the design') and the return payload is described (updated structure plus rendered preview), which annotations cannot convey. It doesn't spell out that the prior image is discarded, but the swap framing implies it.

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 tight sentences, front-loaded with the core action and followed by constraint, persistence, and return value in descending order of importance. The example of valid image sources earns its place; nothing is redundant.

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?

With no output schema and destructive annotations, the description carries the burden well: it covers the mutation's effect, persistence, and both parts of the response. Minor gap is that it doesn't state permission/scope requirements beyond workspace_key.

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 the baseline is 3, but the description earns above baseline by adding a real constraint on image_url — it must be publicly reachable and can come from search_media or get_generated_image — which the schema merely calls 'URL of the new image'. The element parameter's alias/id semantics are left entirely 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 and resource: 'Swap the picture in one image element of an existing design for another image', plus the constraint that size and position are preserved. This clearly distinguishes it from add_design_logo, set_design_background, and add_design_shape without needing 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 a clear precondition — the image URL must be publicly reachable — and points to concrete sibling sources (search_media, get_generated_image). It does not explicitly exclude near-miss alternatives such as add_design_logo or set_design_background, so it stops just short of full when/when-not guidance.

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