Skip to main content
Glama

Generate image

generate_image

Submit an image generation request through Rainbrand’s public API. Use a supported image model returned by list_models and follow its published input schema from get_model. Default to openai/gpt-image-2.5-sunburst for image generation and editing, including work with reference images, unless the user asks otherwise. Create or use a task-specific Brief for the brand identified by brand_session_id, wait for completion, and inspect it. For supported models, pass brief_id alongside the model input; Rainbrand supplies guidance and references while the prompt remains authoritative for content and exact copy. Without brief_id, include relevant brand guidance and references in the model input. Retrieve and inspect outputs with get_generation, then request a Review when useful.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_session_id": "<brand_session_id>",
      "model": "<model>",
      "input": "<input>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesArguments for the selected model, using the field names and reference formats published by get_model.
modelYesModel to run. Choose an ID from list_models whose output type matches the generation tool being called.
brief_idNoCompleted Brief to use for this generation. Rainbrand adds its guidance before your prompt and its visual assets after any references you provide.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
idempotency_keyNoRetry key for recovering the original generation after an uncertain response. Reuse it with identical arguments. Without a key, repeating the request starts another generation.
brand_session_idYesBrand session ID from list_brands for the brand this generation belongs to.

Output Schema

NameRequiredDescriptionDefault
idYesGeneration ID. Pass it as id to get_generation.
statusYesCurrent generation status.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the agent knows this is a non-idempotent external write. The description adds a meaningful behavioral detail the annotations do not: Rainbrand injects its own guidance before the prompt and its visual assets after references when brief_id is supplied, while the prompt stays authoritative for content. It does not mention cost/credit consumption, failure modes, or how long generation typically takes.

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?

Front-loaded with the purpose and default, then workflow in a logical order. It is dense but every sentence carries instruction; the only mild redundancy is repeating 'inspect' for both the Brief and the final outputs.

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

Completeness4/5

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

For a nested-input, async generation tool with an output schema already documenting return values, the description supplies the full surrounding workflow (model discovery, Brief creation, retrieval, review). The remaining gaps are credit cost and error/retry guidance, which the adjacent check_credits and idempotency_key field only partially cover.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description still earns extra credit by explaining how model and input interlock, what brief_id actually contributes behaviorally (guidance insertion), and what to put in input when brief_id is omitted. idempotency_key and llm_model are only handled by the schema, not the prose.

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 opens with a specific verb and resource ('Submit an image generation request'), plus the system it targets, and the image focus separates it cleanly from siblings like generate_audio, generate_video, and apply_brand_edit. It also names the downstream tools (list_models, get_model, get_generation) that surround the call.

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

Usage Guidelines5/5

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

It states exactly which model IDs are valid and where to get them, gives a concrete default (openai/gpt-image-2.5-sunburst) with a condition for when the default applies, and explicitly branches on brief_id presence. Follow-up steps (wait for the Brief, retrieve with get_generation, request a Review) make the when-to-use path unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources