Skip to main content
Glama

generate_image

Create a new image from a text prompt using Google's Gemini multimodal APIs. Provide a detailed description of the image you want to generate.

Instructions

Generate a NEW image from text prompt. Use this ONLY when creating a completely new image, not when modifying an existing one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesText prompt describing the NEW image to create from scratch
modelNoOptional model name to use for image generation (e.g., 'gemini-3.1-flash-image' or 'gemini-3-pro-image'). Defaults to the value of environment variable GEMINI_IMAGE_MODEL, or 'gemini-3.1-flash-image' if unset.
Behavior3/5

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

No annotations provided; description only states creation purpose. Does not disclose side effects, auth needs, rate limits, or output format. Adequate for a simple create tool but minimal depth.

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

Conciseness5/5

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

Single sentence, front-loaded with key action, no wasted words. Perfectly concise.

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?

Given 2 parameters, no annotations, and no output schema, description covers core purpose and usage constraint. Missing return behavior (e.g., image URL or data) but sufficient for basic use.

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 coverage is 100% with good descriptions for both parameters. The tool description adds usage context but does not provide additional meaning beyond schema. Baseline 3 is appropriate.

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?

Description clearly states 'Generate a NEW image from text prompt' with specific verb and resource. Explicitly distinguishes from modifications, differentiating from sibling edit_image.

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

Usage Guidelines4/5

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

Explicitly states when to use: 'ONLY when creating a completely new image, not when modifying an existing one.' Lacks explicit mention of alternative edit_image but exclusion is clear.

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/notfixingit3/nano-banana-mcpv2'

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