Skip to main content
Glama

Background Removal

bg-remove
Read-only

Remove the background from any image, at the image's own size or a smaller one you choose. Returns a transparent PNG. Returns the cut-out as base64 and as a hosted URL, with its format, width and height: a PNG with a transparent background, or WebP (transparent) or JPG (set on white) when you ask for them. Use to isolate the subject of an existing image. To create a new image use images. Cost: 2 credits, charged only when a call succeeds.

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": {
      "image_url": "<image_url>"
    },
    "name": "bg-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoSize of the cut-out: auto is the image's own (up to 25 megapixels), small at most 0.25 megapixels, hd at most 4. Never larger than the image.auto
formatNoImage format of the cut-out.png
image_urlYesPublic URL of the image (JPEG, PNG or WebP, up to 22 MB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "png",
      +  "description": "Image format of the cut-out.",
      +  "enum": [
      +    "png",
      +    "webp",
      +    "jpg"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / image_url / description
      Previous value: -"URL to image."New value: +"Public URL of the image (JPEG, PNG or WebP, up to 22 MB)."
    • changedInput schema / properties / size / description
      Previous value: -"Output resolution."New value: +"Size of the cut-out: auto is the image's own (up to 25 megapixels), small at most 0.25 megapixels, hd at most 4. Never larger than the image."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description correctly spends its words elsewhere: the 2-credit cost with charge-on-success semantics, and the fact that output is both base64 and a hosted URL with format/width/height. It does not state URL lifetime or expiry of the hosted asset, which is the main remaining unknown.

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?

Front-loaded with the action and output, then pricing and routing. Mild redundancy in restating 'transparent PNG' twice across the return sentences, which could be collapsed, but no filler otherwise.

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?

With no output schema, the description carries the return-value burden and does so adequately: format, transparency behavior, base64 plus hosted URL, dimensions. Exact response keys are not given, so an agent knows the shape but not the field names.

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 adds real meaning beyond the schema: that JPG output places the subject on white while WebP stays transparent, and that the cut-out is never larger than the source. This helps an agent choose 'format' and 'size' correctly rather than just enumerating values.

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 the background from any image') plus the sizing scope, and explicitly separates itself from the sibling 'images' tool that creates new images. An agent can pick between bg-remove and images without opening either 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 clear when-to-use ('isolate the subject of an existing image') and names the alternative for the opposite case ('To create a new image use images'). It stops short of exclusions such as non-public URLs or non-image inputs, but the routing decision is unambiguous.

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.