Incarn

Statut d'une animation

get_animation_status

Read-only

Récupère le statut d'un job d'animation et l'URL de la vidéo une fois prête.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	Identifiant du job d'animation.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Identifiant du job.
`error`	Yes	Message d'erreur si le job a échoué, sinon null.
`status`	Yes	Statut du job : en cours, réussi ou échoué.
`photo_url`	Yes	URL de la photo source (avant), pour l'aperçu inline.
`video_url`	Yes	URL de la vidéo une fois prête, sinon null.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 21, 2026

addedOutput schema / properties / photo_url

Added value: +{
+  "description": "URL de la photo source (avant), pour l'aperçu inline.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "video_url",
-  "error"
-]New value: +[
+  "id",
+  "status",
+  "video_url",
+  "error",
+  "photo_url"
+]

Changed1 schema field changedAug 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "description": "Message d'erreur si le job a échoué, sinon null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Identifiant du job.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Statut du job : en cours, réussi ou échoué.",
+      "enum": [
+        "processing",
+        "succeeded",
+        "failed"
+      ],
+      "type": "string"
+    },
+    "video_url": {
+      "description": "URL de la vidéo une fois prête, sinon null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "status",
+    "video_url",
+    "error"
+  ],
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare this as safe and read-only. The description adds the useful detail that the video URL only becomes available when the animation is ready. However, it does not describe behavior such as polling semantics, status values, or error scenarios, though the output schema may cover some of this.

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?

A single sentence delivers exactly the essential information: what is retrieved and what additional data is returned when ready. There is no filler or repetition.

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?

For a simple, one-parameter, read-only status tool with an output schema, the description is nearly sufficient. It clearly states the tool's purpose and the eventual video URL. Slightly more guidance about using it after animate_photo would make it fully complete.

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%, and the only parameter, job_id, is already documented as 'Identifiant du job d'animation'. The description does not need to repeat this and provides no additional syntax or format details, so the baseline of 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?

The description states a specific verb ('Récupère'), a clear resource ('statut d'un job d'animation'), and an additional output detail (video URL once ready). This distinguishes it from sibling tools like animate_photo, confirm_upload, and create_upload, which perform different operations.

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

Usage Guidelines3/5

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

The usage context is implied: this is the status-checking counterpart to animate_photo. However, the description does not explicitly say when to use it, such as after submitting an animation job, nor does it mention any alternatives or exclusions.

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

All Incarn tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Each tool targets a distinct stage of the animation workflow—main action, upload steps, status polling, and examples—and the descriptions cross-reference each other explicitly. Minor ambiguity exists between animate_photo and create_upload as alternative entry points, but the 'prefer image_url' guidance effectively resolves it.

Naming Consistency5/5

All five tools follow a consistent verb_noun snake_case pattern (animate_photo, create_upload, confirm_upload, get_animation_status, list_examples), using clear, predictable verbs throughout. There is no mixing of conventions or vague generic names.

Tool Count4/5

Five tools is well-scoped for the narrow domain of photo animation, with the two upload steps adding necessary surface area for the file-attachment path. Slightly heavy for such a niche service, but each tool earns its place.

Completeness4/5

The core lifecycle is fully covered: upload a photo, animate it, poll status, and view examples. Minor gaps include no credit-balance check despite animation being credit-gated, and no way to list past animations or recover a lost job ID.

Resources

Need Help?