Skip to main content
Glama

Brilliant Design (hosted)

Place an image in a Brilliant design

place_image
Destructive

Use this when the user wants an image (one they attached, or one generated in this conversation) placed into a Brilliant design opened in this conversation: it puts the image on the canvas as an editable image layer, or as the fill of a target layer, and answers how it applied. It takes the design's seed and the image as image (the file attached or generated in the conversation), imageUrl (https) or imageBase64 (PNG, JPEG or WebP, up to 25 MB); target names an existing frame or shape by its id or #ref to fill instead.

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>"
    },
    "name": "place_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new image layer's name (default Image).
seedYesThe slug of a design opened in this conversation (from the design result).
imageNoThe image attached to or generated in the conversation.
targetNoThe id or #ref of an existing frame or shape in the design whose fill becomes the image; its size and position stay. Without it, the image lands as a new layer.
imageUrlNoAn https URL of the image (PNG, JPEG or WebP, up to 25 MB).
imageBase64NoThe image's bytes as base64 (PNG, JPEG or WebP, up to 25 MB).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly carried structurally. The description adds that the tool 'answers how it applied' and that a target's size and position stay, but it never discloses the destructive consequence the annotation implies — that filling a target replaces its existing fill and the design is mutated, with no mention of undo or reversibility. That is the main behavioral fact an agent needs before calling.

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?

Two sentences, front-loaded with the when-to-use trigger before parameter detail, with no filler. It reads as a dense run-on with heavy parenthetical nesting, which slightly hurts scanability but wastes nothing.

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?

An output schema exists, so return-value explanation is not required, and all six parameters are documented in the schema and echoed in the description. The remaining gap is behavioral: the effect of filling an existing frame/shape (what happens to its prior fill, reversibility) is left implicit given the destructive annotation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines seed, name, target, image, imageUrl and imageBase64 with formats, MIME types and the 25 MB limit. The description's contribution is mostly restating them, though the disjunctive framing of the three image sources ('image, imageUrl or imageBase64') and the '#ref or id' targeting hint add modest value beyond the fields.

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?

Names a specific verb and resource ('puts the image on the canvas as an editable image layer, or as the fill of a target layer') and scopes it to a Brilliant design opened in this conversation, which separates it from design/edit_design/inspect_design work. The two application modes (new layer vs. layer fill) are stated outright.

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?

The opening clause gives a clear trigger: the user wants an attached or generated image placed into a design in this conversation. It covers the natural call condition but does not name a sibling tool or state when-not to use it (e.g. removing a background belongs to remove_background).

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