Skip to main content
Glama
SimplyPNG
by SimplyPNG

Remove Background

remove_background

Remove background from image URLs. Choose fast mode for standard images or HD mode for fine edge detail and high resolution.

Instructions

Remove the background from a single image. MANDATORY WORKFLOW — follow these steps in order: (1) Call estimate_credits first (imageCount=1). Show user the cost + balance. Ask for confirmation. (2) Only call this tool AFTER the user confirms. (3) After this returns a jobId, poll get_job_status every 3 seconds until status is "succeeded". (4) Call download_results to get the final download URL. Credit cost: 1 credit (Fast mode, default) or 2 credits (HD mode). Fast mode works with any input size — large images are just downsampled to 2500px output. Use HD only when user needs output above 2500px, or subject has fine edge detail (hair, fur, feathers). refineEdges (requires HD): removes color bleeding at edges — recommend for products on colored backgrounds. No extra credit. IMPORTANT about local files: if user has a local file, do NOT use base64 — base64 tool inputs are stored in the conversation context and a 1MB image consumes ~340k tokens, making the conversation unusable. Instead tell the user: "Please share a public URL for your image (e.g. Google Drive share link, iCloud, Dropbox) or use https://simplypng.app directly."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesHTTPS URL of the image — STRONGLY PREFERRED. Use a URL whenever possible. CRITICAL WARNING about base64: MCP tool inputs are stored in the conversation context. A 1MB image as base64 consumes ~340,000 conversation tokens, quickly making the conversation unusable. Only use base64 for very small images (under 50KB original file size). For local files: tell the user to share a public HTTPS URL (e.g. upload to Google Drive and copy share link, iCloud shared link, Dropbox, or any image hosting). If they have no URL option, direct them to https://simplypng.app instead. Supported URL or base64 formats: JPEG, PNG, WebP, HEIC/HEIF. Base64 server-side size limit: 4MB.
hdModeNoFast mode (default, 1 credit): input resized to 2500px max — OUTPUT capped at 2500px. Works with any input size. HD mode (2 credits): input preserved up to 4096px — OUTPUT up to 4096px. Use HD ONLY when: (1) user explicitly requests HD/high-definition/4K output, (2) user needs output resolution above 2500px, or (3) subject has fine edge detail (hair, fur, feathers). Never use HD based on input size alone — Fast mode handles large inputs fine. Default: false.
backgroundNoBackground fill. transparent requires PNG output. Default: transparent
outputModeNoOutput format. download_url returns a signed URL; base64_json returns raw base64 data. Default: download_url
outputTypeNooriginal: keep original crop. centered: center subject on square canvas. Default: original
refineEdgesNoEnable edge color refinement to remove background color bleeding at subject edges. REQUIRES hdMode: true — the API will return an error if hdMode is false or omitted. No additional credit cost — included in HD mode (2 credits total). Recommend when: subject has complex edges against a strongly or evenly colored background (e.g. product on white/grey backdrop, portrait with solid background).
outputFormatNoOutput file format. Default: png
idempotencyKeyNoOptional idempotency key to prevent duplicate jobs
backgroundColorNoHex color for custom background, e.g. #FF5733
Behavior5/5

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

No annotations provided, but description fully discloses credits (1 or 2), async nature (returns jobId for polling), size limits (2500px fast, 4096px HD), refineEdges requirement, base64 token cost, and output modes. No contradictions.

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?

Long but every sentence earns its place due to complexity. Information is front-loaded (purpose and mandatory workflow), then details. Slightly verbose on base64 warnings but justified by importance.

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?

Covers all aspects: workflow, credit cost, parameter usage, file handling, sibling relationships, and output retrieval (via download_results). No gaps given the complexity and absence of output schema.

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

Parameters5/5

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

Schema has 100% description coverage, but description adds critical context beyond schemas: image parameter includes warnings and workarounds, hdMode explains when to use, refineEdges explains requirement and recommendation. Great added 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 clearly states 'Remove the background from a single image' and differentiates from siblings by indicating the mandatory workflow involving estimate_credits, get_job_status, and download_results. It also contrasts with batch_remove_background (single vs batch).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit step-by-step workflow: call estimate_credits first, show cost, get confirmation, then call this tool, poll get_job_status, call download_results. Also gives guidance on when to use HD mode and refineEdges, and warns against base64 for large files, directing users to use public URLs or simplypng.app.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SimplyPNG/simplypng-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server