Skip to main content
Glama
runapi-ai

grok-imagine-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

upscale_image

Create a RunAPI task to upscale an image from a completed Grok Imagine video task and return task ID, status, and output URLs.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
timeout_msNo
callback_urlNoWebhook URL for terminal Task delivery. Declared type: string.
source_task_idYesCompleted prior Grok Imagine video Task ID. Declared type: string.
poll_interval_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for terminal Task delivery."New value: +"Webhook URL for terminal Task delivery. Declared type: string."
    • changedInput schema / properties / source_task_id / description
      Previous value: -"Completed prior Grok Imagine video Task ID."New value: +"Completed prior Grok Imagine video Task ID. Declared type: string."
  2. Changed3 schema fields changedv0.1.13
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
  3. Changed3 schema fields changedv0.1.11
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Webhook URL for terminal Task delivery.",
+  "type": "string"
+}
    • addedInput schema / properties / source_task_id
      Added value: +{
+  "description": "Completed prior Grok Imagine video Task ID.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "source_task_id"
+]
  4. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It helpfully discloses that this is an async task creation returning a task id, status, and output URLs, which is meaningful context. However, it omits permissions/auth, the meaning of the source_task_id, and — notably — does not reconcile the tool's image-upscale purpose with a parameter documented as accepting a prior *video* task ID.

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?

Two short sentences, front-loaded with the action and backend, with the return shape stated inline. Minimal waste, though '(upscale image)' is slightly redundant with the tool name.

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

Completeness3/5

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

For a task-creation tool with no annotations and no output schema, the description usefully covers the return values. It is still thin on behavioral contract — async semantics, source_task_id requirements, and the image-vs-video inconsistency — so it is only partly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 60%, so the description should compensate, but it adds no input-parameter meaning at all. It says nothing about source_task_id, wait, timeout_ms, callback_url, or poll_interval_ms, leaving half the input contract unexplained.

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 (Create), a named operation (upscale image), and the backend (Grok Imagine task on RunAPI). This distinguishes it from siblings like edit_image and text_to_image, but it doesn't explicitly contrast with the closest alternative (edit_image), keeping it below a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when to prefer this over edit_image or text_to_image. The parenthetical '(upscale image)' only restates the operation rather than routing the agent.

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