Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

execute_commands

Destructive

Execute multiple canvas design commands by ID in sequence, stopping at the first error, and optionally return PNG previews to visually verify results before continuing.

Instructions

Execute one or more commands by ID. Accepts an array of commands that share a single canvasId. Commands run sequentially, stopping on first error. Use command IDs from the skill docs. Pass previewIds + previewScale: 2 for inline PNG verification. Visually inspect every preview, describe what you see, fix issues. (External MCP clients: call init first for usage docs. Hosted-CLI and sub-agents have docs pre-loaded.)

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": {
      "commands": "<commands>"
    },
    "name": "execute_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoOptional: element IDs applied to every command in the batch that names none of its own. The per-command `commands[i].ids` always wins. `elementIds` is accepted as an alias.
projectNoOptional: run THIS call against a project other than the session's bound one: a name or key from list_projects (or an unambiguous name/handle substring), or the absolute path of a project folder (one holding .bl files, or an empty one), which opens in the background and is added to list_projects. Unknown/ambiguous is refused with candidates.
canvasIdNoTarget canvas ID. Required for every canvas-scoped verb (enforced at dispatch, refused by name when missing); the workspace/app-level verbs (get_canvases, create_canvas, create_folder, list_keybindings, the library acts, ...) are exempt and need none.
commandsYesArray of commands to execute sequentially.
sessionIdNoSession ID for per-session visual feedback. Optional.
previewIdsNoElement IDs to include in a PNG preview returned alongside the summary. Omit for no preview.
previewScaleNoScale factor for the preview image (default 1.0, max 3.0). Use 2.0 for verifying visual details like text or alignment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare this as destructive, non-read-only, and non-idempotent. The description adds useful behavior beyond that: commands run sequentially and stop on first error, previews should be visually inspected, and external clients need init first. However, it does not disclose the scope of destructive changes, reversibility, or permission requirements.

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 description is front-loaded with purpose and batch behavior, and its sentences are generally short and useful. The final parenthetical about hosted-CLI and sub-agents plus the imperative preview-inspection workflow are helpful but slightly outside the core tool definition.

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?

Given the rich annotations and fully described schema, the description covers the essential invocation context: batch execution, error behavior, command ID source, preview verification, and init prerequisite. It still leaves some gaps around destructive side effects and the exact return summary, so it is strong but not fully complete.

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 input schema already documents all seven parameters. The description adds actionable meaning beyond the schema by explaining that commands share one canvasId, that command IDs come from the skill docs, and that previewIds and previewScale are used together for inline PNG verification.

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 states a specific verb and resource: 'Execute one or more commands by ID,' and clarifies that the batch shares a single canvasId. It is clear what the tool does, but it does not explicitly distinguish this tool from siblings such as edit or create_modify_elements.

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 gives concrete prerequisites and workflow guidance: use command IDs from skill docs, pass previewIds plus previewScale 2 for verification, and call init first for external MCP clients. It does not state when not to use this tool or which sibling to prefer for higher-level edits.

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