Fotor

Submit Image Task

submit_image_task

Destructive

Starts one Fotor image generation or editing task at native resolution. 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": {
      "model_id": "<model_id>",
      "prompt": "<prompt>"
    },
    "name": "submit_image_task"
  }
}

Input Schema

Name	Required	Description	Default
`extra`	No	Background and format options for models supporting image extras.
`prompt`	Yes	Describe the desired content, style and changes.
`quality`	No	Quality option from list_models; omit to use the model default.
`model_id`	Yes	Model ID from list_models; inspect its supported mode and parameters first.
`image_urls`	No	Reference image URLs (HTTPS), in order. Omit for text-to-image; supply for editing or image guidance.
`resolution`	No	Native output resolution from list_models; auto uses the model default.	auto
`aspect_ratio`	No	Output aspect ratio supported by the model; auto uses its default.	auto

Output Schema

Name	Required	Description	Default
`status`	No	Submission accepted; generation is not yet confirmed complete.	submitted
`task_id`	Yes	Fotor task ID for get_task.
`model_id`	Yes	Model ID used for this task.
`media_type`	Yes	Generated media category.
`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.

Changed13 schema fields changedOct 29, 2026

addedInput schema / properties / aspect_ratio / description

Added value: +"Output aspect ratio supported by the model; auto uses its default."

changedInput schema / properties / extra / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "background": {
-        "default": "auto",
-        "enum": [
-          "transparent",
-          "opaque",
-          "auto"
-        ],
-        "type": "string"
-      },
-      "output_format": {
-        "default": "png",
-        "enum": [
-          "png",
-          "jpeg"
-        ],
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "background": {
+        "default": "auto",
+        "description": "Background treatment; transparent requires a supporting model.",
+        "enum": [
+          "transparent",
+          "opaque",
+          "auto"
+        ],
+        "type": "string"
+      },
+      "output_format": {
+        "default": "png",
+        "description": "Generated image file format.",
+        "enum": [
+          "png",
+          "jpeg"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / extra / description

Added value: +"Background and format options for models supporting image extras."

addedInput schema / properties / image_urls / description

Added value: +"Reference image URLs (HTTPS), in order. Omit for text-to-image; supply for editing or image guidance."

addedInput schema / properties / model_id / description

Added value: +"Model ID from list_models; inspect its supported mode and parameters first."

addedInput schema / properties / prompt / description

Added value: +"Describe the desired content, style and changes."

addedInput schema / properties / quality / description

Added value: +"Quality option from list_models; omit to use the model default."

addedInput schema / properties / resolution / description

Added value: +"Native output resolution from list_models; auto uses the model default."

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: +"Generated media category."
```
addedOutput schema / properties / model_id / description
```
Added value: +"Model ID used for this task."
```

addedOutput schema / properties / status / description

Added value: +"Submission accepted; generation 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.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing cost side effects (consumes Fotor credits, repeats create duplicate tasks and extra charges), the async contract (returns immediately, no polling), and non-retry guidance for uncertain submissions. It also bounds scope by ruling out credit purchase/checkout, which the destructiveHint and idempotentHint flags cannot convey on their own.

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 and cost warning; every sentence carries decision-relevant information. Minor redundancy: "Returns a task ID without waiting for completion" is restated by "This tool does not poll for completion," costing one sentence of efficiency.

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?

With an output schema handling return shape and rich annotations covering safety, the description only needed to cover cost, async behavior, and retry semantics — all present. The remaining gap is that it doesn't clarify model-dependent mode support (generation vs editing) beyond pointing at list_models.

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 coverage is 100%, so every parameter is already documented in-schema (model_id from list_models, image_urls for editing vs omit for text-to-image, resolution/quality from list_models). The description adds only the phrase "at native resolution" and otherwise defers to the schema, so baseline 3 applies.

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 generation or editing task") plus the distinguishing behavior (returns a task ID without waiting). It separates itself from the polling sibling by naming get_task and explicitly disclaiming polling, so an agent can route correctly without opening a schema.

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 when-to-use context and exclusions: use get_task once for status, do not auto-retry on uncertain outcomes, this tool does not purchase credits. It does not, however, contrast with the other submit_* siblings (e.g. submit_image_upscale_task) to help the agent pick the right image task type.

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?