Skip to main content
Glama
runapi-ai

Ideogram V3 MCP Server

by runapi-ai

edit_image

Edit images using Ideogram V3 models. Submit a source image URL and receive edited outputs with task status and URLs.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNo
output_countNo
rendering_speedNo
source_image_urlNo
waitNoPoll until the task reaches a terminal status.
timeout_msNo
poll_interval_msNo
modelNoRunAPI model slug for this model line.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions returning a task id, status, and output URLs, but does not explicitly state that it is an async task, nor disclose side effects, permissions, or error behavior. The presence of wait and timeout parameters hints at polling, but it is not clarified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, but it redundantly includes the tool name in parentheses. It is concise but could be more efficient by removing the parenthetical clarification.

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

Completeness1/5

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

With 8 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain key aspects like source_image_url, style, or the overall task lifecycle.

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

Parameters1/5

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

Schema description coverage is only 25% (2 of 8 parameters have descriptions). The tool description adds no additional meaning for the parameters, failing to compensate for the low coverage.

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 it creates an Ideogram V3 task for editing images, which aligns with the tool name. However, it does not differentiate from sibling tools like reframe_image or remix_image, which are also likely image editing tasks.

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?

No guidance on when to use this tool versus alternatives. No context on prerequisites or scenario suitability.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runapi-ai/ideogram-v3-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server