Fotor

Submit Image Upscale Task

submit_image_upscale_task

Destructive

Starts one Fotor image upscaling task. 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_image_upscale_task"
  }
}

Input Schema

Name	Required	Description	Default
`image_url`	Yes	Accessible HTTPS image URL, such as file_url after upload.
`upscale_ratio`	No	Image enlargement factor; output width and height are capped at 2048 pixels.

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.

Changed7 schema fields changedOct 29, 2026

addedInput schema / properties / image_url / description

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

changedInput schema / properties / upscale_ratio / description

Previous value: -"Image enlargement factor; defaults to 2x."New value: +"Image enlargement factor; output width and height are capped at 2048 pixels."

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 already declare non-idempotent, destructive, open-world; the description concretizes what that means: credit consumption, a duplicate task being created on repeat, no polling, and a 'do not auto-retry' rule for ambiguous outcomes. That is real operational context beyond the structured hints, not a restatement of them.

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 core action, with the cost and async caveats following. Slight redundancy between 'without waiting for completion' and 'does not poll for completion', but the repetition serves emphasis on the highest-risk misuse.

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?

An output schema exists, so return-shape explanation is unnecessary; the description covers everything else an agent needs for a fire-and-forget async submission: cost, non-idempotency, no polling, no retry, and no checkout side effect.

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% and both parameters are already documented (HTTPS URL, ratio with the 2048px cap), so the schema carries the load. The description adds no parameter-level detail such as URL constraints, size limits, or ratio guidance, making 3 the appropriate baseline.

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 Fotor image upscaling task'), which is separable from the other submit_* siblings that generate, remove backgrounds, or separate audio. The word 'upscaling' plus the mention of credits and async task IDs pins the capability precisely.

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 routes follow-up work to get_task and bounds it ('check its status once'), forbids polling, and warns against automatic retry when the outcome is uncertain. It also excludes an adjacent workflow ('does not purchase credits or initiate a checkout flow'), so an agent knows which sibling handles that need.

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?