Skip to main content
Glama

Remove background

remove_background

Remove the background from an image and return a transparent PNG/WebP, or place the subject on white, a colour, a gradient or a built-in scene, optionally at a marketplace size (Amazon, Shopify, Etsy, eBay, Instagram). Costs 1 credit (hd 2, ultra 4); free credits export up to 2 MP.

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
cropNoTrim the result to the subject.
sizeNooriginal: Same pixels as your upload; amazon: 2000², pure white, product fills ~85%; shopify: 2048² square, zoom-ready; etsy: 2000×1600, 5:4 thumbnail-safe; ebay: 1600², white; instagram: 1080×1350 portrait post; story: 1080×1920 vertical
formatNoOutput format. png keeps transparency everywhere; webp is smaller; jpg has no transparency.
shadowNoAdd a shadow under the subject when it's placed on a background.
qualityNopreview 0.25 MP, standard 4 MP (default), hd 25 MP, ultra 50 MP. hd and ultra need paid credits.
subjectNomain drops small stray objects and keeps the main subject.
image_urlNoPublic http(s) URL of a JPG, PNG or WebP image (up to 25 MB).
backgroundNotransparent (default), white, a hex colour such as #F5F5F5, gradient:#a,#b, or scene:<id> with one of: plinth, marble, linen, pastel, noir, garden, kitchen, concrete, signal, festive.
image_base64NoThe image as base64 (or a data: URL), if there is no public URL. Prefer image_url for large files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare openWorldHint=true, readOnlyHint=false, and destructiveHint=false, so the description is not required to establish the safety profile. It nonetheless adds genuinely useful context the annotations do not carry: per-call credit pricing by quality tier and the 2 MP export ceiling on free credits. It omits other operational traits, such as how the image is transmitted or processed, or what happens on failure, keeping it below a 5.

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 primary action, followed by the output variants and then cost, which is a sensible ordering for an agent scanning the definition. Two sentences, no filler, though the first sentence is long and clause-dense enough to be slightly harder to parse than necessary.

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?

For a 9-parameter tool with full schema coverage, no output schema, and annotations covering safety, this is nearly sufficient: it names the return artefact and the cost model. The notable omission is that no parameter is marked required, so the description should state that exactly one of image_url or image_base64 must be supplied; it never clarifies that dependency.

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 description coverage is 100%, so the schema already documents every parameter, including the marketplace size table, the shadow and subject semantics, and the background syntax. The description paraphrases that option space ("transparent PNG/WebP", "marketplace size") without adding new syntax. Its only genuinely additive detail is the credit mapping to quality tiers ("hd 2, ultra 4"), which goes beyond the schema's vaguer "hd and ultra need paid credits".

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 an image) and then enumerates the exact outcomes: transparent PNG/WebP, or subject composited onto white, a colour, a gradient, or a built-in scene. None of the named siblings (erase_objects, upscale_image, get_credits) overlap this operation, so an agent can route to it unambiguously from the first clause.

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 decision context through the option space (transparency vs. composite, marketplace presets) and through economics ("costs 1 credit (hd 2, ultra 4); free credits export up to 2 MP"), which lets an agent pick a quality tier sensibly. It stops short of naming alternatives or exclusion conditions, such as when to prefer erase_objects or upscale_image instead, so it is not a full 5.

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.