Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Move design element

move_design_element
DestructiveIdempotent

Move one element of an existing design to a new position. x and y are the new top-left corner in design pixels (a 1080x1350 slide runs from 0,0 to 1080,1350); pass either or both. Use the bounding boxes in the design structure to place 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>"
    },
    "name": "move_design_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoNew left edge, in design pixels.
yNoNew top edge, in design pixels.
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, idempotentHint=true, and readOnlyHint=false, so the bar is lower. The description still adds real value: 'The change is saved to the design' discloses persistence, and it describes the return payload (updated design structure plus rendered preview) in the absence of an output schema. It does not explain why the operation is flagged destructive (e.g. overwriting the prior position), which would be the remaining gap.

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?

Front-loaded with the action, then coordinate semantics, then side effects and return value. Every sentence contributes new information with no restatement of the name or schema.

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 5-parameter mutation with no output schema, the description covers the action, coordinate system, persistence, and response shape, which is enough to call it correctly. Minor gaps: no permission/workspace prerequisites and no guidance on obtaining element aliases beyond pointing at the design structure (left to the schema).

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 goes further by giving the coordinate space concretely ('a 1080x1350 slide runs from 0,0 to 1080,1350') and clarifying that x/y may be passed independently. That is meaningfully beyond the schema's 'New left edge, in design pixels.'

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 ('Move one element of an existing design to a new position') and is immediately distinguishable from siblings like recolor_design_element, set_design_element_width, and remove_design_element. An agent can tell exactly which mutation this performs 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?

'pass either or both' clarifies partial moves, and 'Use the bounding boxes in the design structure to place it' implies the workflow (read structure, then move). No explicit when-not or named alternative, and no mention that the design id comes from compose_design/generate_post (that is only in the schema), so it stops short of a 5.

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