Skip to main content
Glama

Brilliant Design (hosted)

Remove a photo's background

remove_background

Use this when the user attaches or links a photo and asks to remove its background, cut out the subject or get a transparent PNG. It returns the user's own photo with the background cut away by a matte, at its original size up to 2,048 pixels on the long edge, every subject pixel unchanged. Do not use to generate a new image. It cuts the subject out of the original photo with a matte. It takes the user's image as image (a file the user attached), imageUrl (https) or imageBase64, and returns the cutout, a share link, and Open in Brilliant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNoThe photo the user attached.
imageUrlNoAn https URL of the photo (PNG, JPEG or WebP, up to 25 MB).
mimeTypeNoThe mime type of imageBase64 (optional, the bytes are sniffed).
imageBase64NoThe photo's bytes as base64 (PNG, JPEG or WebP, up to 25 MB).

Output Schema

NameRequiredDescriptionDefault
heldNo
widthYes
heightYes
openUrlNo
matteUrlNo
shareUrlNo
originalUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic profile (readOnly=false, destructive=false, openWorld=true, idempotent=false); the description adds real substance beyond them: the output is the user's own photo, matte-cut, at original size capped at 2,048 px on the long edge, with every subject pixel unchanged. It also discloses what the call returns (cutout, share link, 'Open in Brilliant'), which is behavioral context the annotations cannot carry.

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 trigger condition is front-loaded and the exclusion follows immediately, so the most decision-relevant content comes first. The sentence 'It cuts the subject out of the original photo with a matte' largely restates the earlier 'background cut away by a matte' clause and could be dropped.

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 transformation tool with an output schema already present, the description covers what an agent needs: the trigger, the negative case, the three input modes, fidelity and size limits. Return-value detail is redundant with the output schema but harmless, and no decision-critical gap remains.

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 adds the meaningful fact that image, imageUrl and imageBase64 are alternative input modes with 'a file the user attached' framing. That either/or relationship is not spelled out in the schema, so it earns a modest bump above baseline.

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 ('remove its background', 'cut out the subject', 'transparent PNG') and explicitly separates itself from image generation with 'Do not use to generate a new image'. An agent can distinguish this from design/edit_design/place_image without opening any 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 concrete trigger condition ('when the user attaches or links a photo and asks to remove its background, cut out the subject or get a transparent PNG') plus an explicit exclusion ('Do not use to generate a new image'). It does not name the specific sibling tool to use for the generative case, so the alternative is described by behavior rather than by name.

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