grok-imagine-mcp

segment_map

Creates a Grok Imagine segmentation task on RunAPI from an image URL, returning a task ID, status, and output URLs, with optional polling until completion.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "segment_map"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`image_url`	No	Public image URL that the service can fetch. Declared type: string.
`timeout_ms`	No
`callback_url`	No	Webhook URL for terminal Task delivery. Declared type: string.
`source_task_id`	No	Completed Image 2.0 text-to-image Task ID owned by the same account. Compatibility input; use image_url instead. Declared type: string.
`poll_interval_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.2.0Oct 3, 2026

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 / image_url / description

Previous value: -"Public image URL that the service can fetch."New value: +"Public image URL that the service can fetch. Declared type: string."

removedInput schema / properties / model / enum

Removed value: -[
-  "grok-imagine-image-2-0"
-]

changedInput schema / properties / source_task_id / description

Previous value: -"Completed Image 2.0 text-to-image Task ID owned by the same account. Compatibility input; use image_url instead."New value: +"Completed Image 2.0 text-to-image Task ID owned by the same account. Compatibility input; use image_url instead. Declared type: string."

addedInput schema / required
```
Added value: +[]
```

Addedv0.1.13Aug 26, 2026

TDQS

C2.8/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, and it does disclose the return shape (task id, status, output URLs) and implies async task creation. It omits other important traits: whether this is a paid/consuming operation, auth requirements, and the polling behavior implied by the wait/poll_interval_ms parameters.

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 compact sentences, front-loaded with the action and followed by the return contract. Nothing is padded, though the parenthetical '(segment map)' is low-value restatement.

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 7-parameter task-creation tool with no annotations and no output schema, stating the return values is genuinely useful. But the description leaves the tool's actual semantics ('segment map'), usage context, and the async/polling lifecycle unaddressed, so an agent still needs the sibling get_task to close the loop by inference.

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 coverage is 71%, leaving timeout_ms and poll_interval_ms with no documented meaning in either place. The description adds no parameter guidance at all, so it fails to compensate for the coverage gap on a 7-parameter tool.

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

Purpose3/5

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

States a specific verb and resource ('Create a Grok Imagine task on RunAPI') and names the operation type ('segment map'). However, '(segment map)' merely restates the tool name, and nothing distinguishes this from siblings like edit_image, text_to_image, or image_to_video that also create Grok Imagine tasks. The agent can tell it creates a task but not what a 'segment map' produces.

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 alternatives among the many sibling task-creation tools. The only hint of routing ('use image_url instead') lives in the source_task_id parameter description, not the tool description.

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

Deploy Server