Skip to main content
Glama
poof-bg

Poof Background Removal MCP Server

by poof-bg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

remove_background

Remove image backgrounds by providing a URL or base64-encoded image. Get a transparency-ready result, with optional resizing, cropping, and format selection.

Instructions

Remove the background from an image. Returns the processed image as base64. Accepts URL or base64-encoded image. Can also resize the result to an exact width x height without stretching (width, height, fit).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fitNoHow to fit the image into width x height. 'contain' pads the remaining area (transparent or bg_color), 'cover' fills the canvas and crops the overflow around the subject, 'scale-down' is like contain but never enlarges a smaller imagecontain
cropNoWhether to crop the image to the subject bounds
sizeNoOutput image size preset (megapixel cap). Ignored when width or height is setfull
imageYesImage input: base64-encoded image data or a URL to an image
widthNoOutput width in pixels. On its own, the height follows the aspect ratio. With height, the image is fitted into an exact width x height canvas without stretching
formatNoOutput image formatpng
heightNoOutput height in pixels. On its own, the width follows the aspect ratio. With width, the image is fitted into an exact width x height canvas without stretching
bg_colorNoBackground color (hex, rgb, or color name). Only applies when channels is 'rgb'. Example: '#ffffff'
channelsNoOutput color channels. Use 'rgba' for transparency, 'rgb' for opaque backgroundrgba

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.0
    • addedInput schema / properties / fit
      Added value: +{
+  "default": "contain",
+  "description": "How to fit the image into width x height. 'contain' pads the remaining area (transparent or bg_color), 'cover' fills the canvas and crops the overflow around the subject, 'scale-down' is like contain but never enlarges a smaller image",
+  "enum": [
+    "contain",
+    "cover",
+    "scale-down"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / height
      Added value: +{
+  "description": "Output height in pixels. On its own, the width follows the aspect ratio. With width, the image is fitted into an exact width x height canvas without stretching",
+  "maximum": 6000,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / size / description
      Previous value: -"Output image size preset"New value: +"Output image size preset (megapixel cap). Ignored when width or height is set"
    • changedInput schema / properties / size / enum
      Previous value: -[
-  "full",
-  "preview",
-  "small",
-  "medium",
-  "large"
-]New value: +[
+  "full",
+  "preview",
+  "medium",
+  "hd"
+]
    • addedInput schema / properties / width
      Added value: +{
+  "description": "Output width in pixels. On its own, the height follows the aspect ratio. With height, the image is fitted into an exact width x height canvas without stretching",
+  "maximum": 6000,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose key behavioral traits: 'Returns the processed image as base64' and 'Accepts URL or base64-encoded image.' However, it does not mention potential error conditions, limits, side effects, or whether the operation is stateless. It adds some behavioral transparency but not comprehensive context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The primary purpose is front-loaded, followed by output format, input types, and optional resizing capability. Every sentence contributes useful information, and the structure makes it easy to scan.

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 tool with 9 parameters and no output schema, the description provides a complete high-level view: what it does, accepted inputs, return format, and the key resizing behavior. The schema supplies detailed parameter semantics, so the description need not repeat them. It lacks explicit error handling or limitations, but the essential information for correct invocation is present.

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 baseline is 3. The description mentions width, height, and fit in passing but does not add meaning beyond the schema's detailed parameter descriptions. The schema already fully documents each parameter, so the description adds minimal additional semantic value.

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?

The description uses a specific verb and resource: 'Remove the background from an image.' It clearly distinguishes itself from the only sibling, get_account, which serves a completely different purpose. The statement is unambiguous and instantly conveys the tool's core function.

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 description provides clear context about when to use the tool: whenever background removal is needed. It states the accepted input types (URL or base64) and the available resizing behavior, giving enough context for an agent to select it. It does not explicitly mention when not to use it or list alternatives, but no close alternatives exist among siblings, so this is a minor gap.

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

Deploy Server

Other Tools