Skip to main content
Glama
runapi-ai

grok-imagine-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edit_image

Create a Grok Imagine task on RunAPI to edit images, returning a task ID, status, and output URLs.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
promptNoOptional image editing instruction. Declared type: string.
timeout_msNo
aspect_ratioNoDeclared type: string.
callback_urlNoWebhook URL for terminal Task delivery. Declared type: string.
mask_indicesNoNot accepted by this model.
source_task_idNoNot accepted by this model.
poll_interval_msNo
source_image_urlNoPublic source image URL. Declared type: string.
source_image_urlsNoDeclared type: array.
enable_safety_checkerNoEnable content safety checks. Declared type: boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / aspect_ratio / description
      Added value: +"Declared type: string."
    • 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 / enable_safety_checker / description
      Previous value: -"Enable content safety checks."New value: +"Enable content safety checks. Declared type: boolean."
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "grok-imagine-edit-image",
-  "grok-imagine-image-2-0"
-]
    • changedInput schema / properties / prompt / description
      Previous value: -"Optional image editing instruction."New value: +"Optional image editing instruction. Declared type: string."
    • changedInput schema / properties / source_image_url / description
      Previous value: -"Public source image URL."New value: +"Public source image URL. Declared type: string."
    • addedInput schema / properties / source_image_urls / description
      Added value: +"Declared type: array."
    • addedInput schema / required
      Added value: +[]
  2. Changed9 schema fields changedv0.1.13
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / aspect_ratio
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / mask_indices
      Added value: +{
+  "description": "Not accepted by this model."
+}
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "grok-imagine-edit-image"
-]New value: +[
+  "grok-imagine-edit-image",
+  "grok-imagine-image-2-0"
+]
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / source_image_urls
      Added value: +{
+  "items": {},
+  "type": "array"
+}
    • addedInput schema / properties / source_task_id
      Added value: +{
+  "description": "Not accepted by this model."
+}
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
    • removedInput schema / required
      Removed value: -[
-  "source_image_url"
-]
  3. Changed5 schema fields changedv0.1.11
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Webhook URL for terminal Task delivery.",
+  "type": "string"
+}
    • addedInput schema / properties / enable_safety_checker
      Added value: +{
+  "description": "Enable content safety checks.",
+  "type": "boolean"
+}
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "Optional image editing instruction.",
+  "type": "string"
+}
    • addedInput schema / properties / source_image_url
      Added value: +{
+  "description": "Public source image URL.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "source_image_url"
+]
  4. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose the async task model and the return shape (task id, status, output URLs), but omits auth requirements, that wait defaults to true and triggers polling, and that some declared parameters are rejected by this model.

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 resource, and no filler. Slightly jargon-heavy ('Grok Imagine task on RunAPI') but efficient overall.

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 12-parameter, zero-required, no-output-schema tool with no annotations, the description covers purpose and return values but leaves polling behavior, the default wait=true, and rejected-parameter caveats unexplained. Adequate but with clear gaps.

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 83%, above the 80% threshold, so the schema already documents most parameters. The description adds no parameter-level detail such as prompt format, aspect ratio values, or callback semantics, 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?

The description states a specific verb and resource: creating a Grok Imagine task for image editing on RunAPI. 'edit image' distinguishes it reasonably from siblings like text_to_image and upscale_image, though it never explicitly contrasts itself with them.

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 mention of alternatives (e.g., upscale_image, text_to_image), and no prerequisites such as needing a source image URL. The agent must infer all routing decisions from the name alone.

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