Skip to main content
Glama

flow_generate_image

Generate 1–4 images from a text prompt with Nano Banana models, including controls for aspect ratio, image size, style, presets, and negative prompts.

Instructions

Generate 1-4 images from a text prompt with a Nano Banana model.

Args: prompt: Description of the image. Text inside quotes is rendered as on-image text. model: 'fast' (Nano Banana 2.1, default), 'pro' (Nano Banana Pro), 'lite', or a full model id. number_of_images: 1-4 (each image is a separate request and is billed separately). aspect_ratio: e.g. '1:1', '2:3', '3:4', '4:5', '9:16', '16:9', '21:9'. Overrides preset. image_size: '1K', '2K' or '4K'. Overrides preset. Lite supports 1K only. preset: Format preset, e.g. 'youtube-thumbnail', 'shorts', 'pinterest-pin', 'worksheet'. style: Style preset, e.g. 'photo', 'watercolor', 'kids-book', 'infographic'. negative_prompt: Things to avoid. output_dir: Override the output folder.

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": {
      "prompt": "<prompt>"
    },
    "name": "flow_generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
styleNo
presetNo
promptYes
image_sizeNo
output_dirNo
aspect_ratioNo
negative_promptNo
number_of_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the full behavioral burden. It usefully discloses per-image billing and the Lite 1K-only constraint, but it does not explain where generated images are written, what is returned, or whether output_dir creation has side effects.

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?

The first sentence is front-loaded and the argument list is compact and readable. It includes useful constraints without excessive prose, though the Args block format is slightly repetitive.

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 nine-parameter generation tool with no annotations and no output schema, the parameter explanations are strong. However, the definition is incomplete about return values and how this tool relates to sibling alternatives, which an agent needs in order to choose and invoke it confidently.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: it explains prompt quoting behavior, model aliases and default, image count and billing implications, aspect ratio examples and override behavior, image size values and Lite limitations, preset/style examples, negative prompts, and output_dir override.

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 clear verb and resource: generate 1-4 images from a text prompt using a Nano Banana model. It does not explicitly distinguish this tool from siblings such as flow_generate_image_with_references or flow_edit_image, leaving the agent to infer the difference.

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?

The description gives defaults and constraints but no explicit guidance on when to use this tool rather than flow_generate_image_with_references or flow_edit_image. The agent must infer that this is the plain text-to-image path from the tool name and prompt-only input.

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