Skip to main content
Glama

Brilliant Design (hosted)

Add rows to a Brilliant design

edit_design
Destructive

Use this when the user wants to change, restyle or add to a Brilliant design opened in this conversation, such as adding a section or a screen next to it, changing the copy or the colors, or making it darker. It takes the design's seed and Blueprint rows and applies them on that design's canvas: new rows add layers, and a row that leads with an id or #ref the design already has changes that layer. It returns how the rows applied, naming any row that did not apply. Its rows run up to 8,000 characters per call; a call of about 20 rows (about 1,500 characters), such as a page's frame and its first section, lands on the canvas within a few seconds. Rows take literal values (hex colors, numbers); design tokens are not available in this lane.

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": {
      "seed": "<seed>",
      "blueprint": "<blueprint>"
    },
    "name": "edit_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedYesThe slug of a design opened in this conversation (from the design result).
blueprintYesReadable design rows, one element per line: its kind, text, size and colors in short form. Example: t("Sign in",Inter,15,b) f[(#FFFFFF)] is the bold white 15 px Inter text "Sign in". Children sit indented two spaces under their parent; no file() row; literal values (hex colors, numbers). Placeholder copy shows a person as a role label ("Account owner", "Home cook") rather than a first and last name: a profile, a name field's sample value and a testimonial's author alike. Brilliant applies rows as they arrive and the canvas animates each batch in, so a design reads best when its first rows set the frame and its main sections and later rows fill in the details.

Output Schema

NameRequiredDescriptionDefault
slugYes
turnYes
haltsNo
renderNo
repeatNo
resultNo
appliedYes
outcomeNo
pendingNo
elementsNo
diagnosticsNo
canvasOpenedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructive/non-idempotent annotations, it discloses exactly what happens on the canvas: new rows add layers, rows leading with an id or #ref mutate existing layers, and the response names rows that failed to apply. It also gives concrete operational limits (8,000 characters, ~20 rows, a few seconds) and warns that design tokens are unavailable in this lane, which is real behavioral context an agent could not get from annotations.

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 first sentence front-loads the trigger and the core action, and each subsequent sentence carries a distinct fact (row semantics, return behavior, limits, token restriction). It is dense but a little crowded, with the latency/row-count detail bordering on more than an agent needs to select and call the tool.

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?

For a destructive two-parameter mutation tool with an output schema, this covers everything an agent needs: when to call it, how rows are interpreted, what happens to existing layers, failure reporting, and size/latency expectations. Nothing essential is left to inference.

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 already 100%, so the baseline is 3, but the description adds meaning the schema does not spell out as directly — the id/#ref leading-row convention for mutating versus adding layers, and the literal-value-only constraint. The 8,000-character cap is restated from the schema, which is mild redundancy.

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 concrete verb and resource — change, restyle or add to a Brilliant design, with examples like adding a section, changing copy or colors. It implicitly separates this from read-oriented siblings by framing it as the lane that 'applies them on that design's canvas', but it never names an alternative tool explicitly.

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 states a clear triggering condition: 'Use this when the user wants to change, restyle or add to a Brilliant design opened in this conversation', including the precondition that the design is already open. It stops short of saying when not to use it or naming the sibling that handles inspection versus mutation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources