Skip to main content
Glama
Sign In

Fotor

by com.fotor.mcp
OverviewDiscussionsAdmin

Get Task

get_task
Read-onlyIdempotent

Check an image, video, audio or image-processing task once.

Uses existing account credentials; creates no tasks or credentials and consumes no credits. Does not poll or post-process results.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesFotor task ID returned by a submission tool.

Output Schema

NameRequiredDescriptionDefault
errorNoStable failure code; null when no failure is reported.
statusYesObserved task state. processing does not distinguish queued or running; unknown is an unrecognized upstream state.
task_idYesFotor task ID for get_task.
task_typeNoAudio operation type when available.
result_urlNoCompleted output URL; availability is not guaranteed permanently. Audio output may be MP3 or ZIP.
is_terminalYesWhether the task has completed, failed, timed out or been cancelled.
failure_reasonNoSafe failure summary; may be generic rather than the upstream root cause.
credits_incrementNoReported task credit cost; not an additional charge on each query. Null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / task_id / description
      Added value: +"Fotor task ID returned by a submission tool."
    • 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 / error / description
      Added value: +"Stable failure code; null when no failure is reported."
    • addedOutput schema / properties / failure_reason
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Safe failure summary; may be generic rather than the upstream root cause."
+}
    • addedOutput schema / properties / is_terminal / description
      Added value: +"Whether the task has completed, failed, timed out or been cancelled."
    • addedOutput schema / properties / result_url / description
      Added value: +"Completed output URL; availability is not guaranteed permanently. Audio output may be MP3 or ZIP."
    • addedOutput schema / properties / status / description
      Added value: +"Observed task state. processing does not distinguish queued or running; unknown is an unrecognized upstream state."
    • addedOutput schema / properties / task_id / description
      Added value: +"Fotor task ID for get_task."
    • addedOutput schema / properties / task_type
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Audio operation type when available."
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: no credit consumption, no credential/task creation, and explicitly no polling or post-processing. It does not describe error or pending-state handling, which keeps it below 5.

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?

Three short sentences, front-loaded with the resource and action, followed by the credential/credit note and the non-polling constraint. No filler and every sentence carries information.

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?

An output schema exists, so return values need not be explained, and the description covers side effects, cost and the single-shot read model. What remains unstated is what an agent should do if the task is still pending or failed, which is a real but modest gap.

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 the single task_id parameter is already documented in the schema as 'Fotor task ID returned by a submission tool'. The description adds no format, encoding or lookup guidance beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check an image, video, audio or image-processing task once') and the task types it covers, which lets an agent separate it from the many submit_* siblings. 'Check' is slightly less precise than 'retrieve status/result', but the second sentence sharpens the scope (no polling, no post-processing).

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?

'Uses existing account credentials; creates no tasks or credentials and consumes no credits' plus 'Does not poll or post-process results' establishes clear usage context: call it once after a submit_* tool returns a task ID. It never names an alternative tool or states an explicit when-not-to-use condition, so it falls short of a 5.

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

All Fotor toolsInspect
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