Skip to main content
Glama
runapi-ai

grok-imagine-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

extend_video

Extend a previously generated video by creating a continuation task with a new prompt, specifying start second and extension duration, then retrieve task status and output URLs.

Instructions

Create a Grok Imagine task on RunAPI (extend video). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
promptYesVideo continuation prompt.
timeout_msNo
callback_urlNoWebhook URL for terminal Task delivery.
start_secondsYesSource video position in seconds where extension begins.
source_task_idYesCompleted prior Grok Imagine video Task ID.
poll_interval_msNo
extension_duration_secondsYesExtension duration in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.13
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / extension_duration_seconds / anyOf
      Added value: +[
+  {
+    "const": 6,
+    "type": "number"
+  },
+  {
+    "const": 10,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / extension_duration_seconds / enum
      Removed value: -[
-  6,
-  10
-]
    • removedInput schema / properties / extension_duration_seconds / type
      Removed value: -"number"
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
  2. Changed6 schema fields changedv0.1.11
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Webhook URL for terminal Task delivery.",
+  "type": "string"
+}
    • addedInput schema / properties / extension_duration_seconds / description
      Added value: +"Extension duration in seconds."
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Video continuation prompt.",
+  "maxLength": 5000,
+  "type": "string"
+}
    • addedInput schema / properties / source_task_id
      Added value: +{
+  "description": "Completed prior Grok Imagine video Task ID.",
+  "type": "string"
+}
    • addedInput schema / properties / start_seconds
      Added value: +{
+  "description": "Source video position in seconds where extension begins.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "source_task_id",
+  "prompt",
+  "start_seconds",
+  "extension_duration_seconds"
+]
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that it returns a task id, status, and output URLs, but it does not mention whether the call is synchronous, that polling behavior exists (despite the wait parameter), or any side effects or constraints. The verb 'Create' implies a write operation, but no further behavioral context is given.

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?

The description is a single sentence that front-loads the core action: 'Create a Grok Imagine task on RunAPI (extend video)'. It then adds the return type. No wasted words, and the structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is inadequate for a complex tool with no output schema and no annotations. It does not explain the concept of video extension, the dependency on a source_task_id from a completed prior task, or what the output URLs represent. A new agent is left without essential operational context.

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 75%, so most parameters already have descriptions. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 action and resource: 'Create a Grok Imagine task on RunAPI (extend video)'. The qualifier 'extend video' clearly distinguishes it from siblings like text_to_video and image_to_video, making the tool's purpose unambiguous.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives. It does not mention that it requires a prior completed video task, nor does it exclude other scenarios. The only implicit clue is the name and 'extend video', but there is no explicit when-to-use or when-not-to-use information.

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

Deploy Server

Other Tools