Fotor

Submit Background Removal Task

submit_background_removal_task

Destructive

Starts one Fotor background removal task that returns a transparent image. May consume existing Fotor credits. Returns a task ID without waiting for completion; use get_task to check its status once. This tool does not poll for completion. Repeating the request may create another task and consume additional credits. Do not automatically retry when the submission outcome is uncertain. This tool does not purchase credits or initiate a checkout flow.

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": "submit_background_removal_task"
  }
}

Input Schema

Name	Required	Description	Default
`image_url`	Yes	Accessible HTTPS image URL, such as file_url after upload.

Output Schema

Name	Required	Description	Default
`status`	No	Submission accepted; processing is not yet confirmed complete.	submitted
`task_id`	Yes	Fotor task ID for get_task.
`operation`	Yes	Image processing operation performed.
`media_type`	No	Processed media category.	image
`credits_increment`	No	Reported task credit cost; not an additional charge on each query. Null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / image_url / description

Added value: +"Accessible HTTPS image URL, such as file_url after upload."

addedOutput schema / properties / credits_increment / description

Added value: +"Reported task credit cost; not an additional charge on each query. Null if unavailable."

addedOutput schema / properties / media_type / description
```
Added value: +"Processed media category."
```
addedOutput schema / properties / operation / description
```
Added value: +"Image processing operation performed."
```

addedOutput schema / properties / status / description

Added value: +"Submission accepted; processing is not yet confirmed complete."

addedOutput schema / properties / task_id / description
```
Added value: +"Fotor task ID for get_task."
```

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare destructiveHint/idempotentHint=false, but the description adds the operational consequences the agent actually needs: credits may be consumed, repeats may create a second paid task, submission is non-blocking, and ambiguous outcomes must not be retried. That is precisely the risk context the hints cannot express.

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 purpose and cost warning, and every sentence is actionable. Minor redundancy between 'without waiting for completion' and 'does not poll for completion' — the same point made twice.

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?

Output schema exists, so return-shape explanation is unnecessary; the description still tells the agent it gets a task ID back and where to go next. Cost, idempotency risk, and non-polling behavior are all covered for an open-world, destructive submission tool.

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?

One parameter with 100% schema description coverage, so the schema already explains image_url (accessible HTTPS URL, e.g. file_url after upload). The prose adds no format, size, or constraint detail beyond it — baseline 3 for a fully-documented single parameter.

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: starts one background removal task producing a transparent image. The resource is distinct from every sibling (upscale, audio separation, text-to-video, etc.), so an agent can select it by name alone.

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?

Explicitly names the follow-up tool ('use get_task to check its status once'), states the anti-pattern ('Do not automatically retry when the submission outcome is uncertain'), and rules out an adjacent flow ('does not purchase credits or initiate a checkout flow'). When-to-use, when-not-to-use, and the alternative are all present.

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

All Fotor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?