Skip to main content
Glama

batch_generate

Generate multiple images simultaneously by providing a list of text prompts. Specify model, aspect ratio, format, and quality for consistent batch output.

Instructions

Generate multiple images in parallel from a list of prompts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel to use for all generations (optional)
promptsYesList of text prompts (1-10)
qualityNoQuality preset (fast, balanced, quality)
aspect_ratioNoAspect ratio for all images (default: 1:1)1:1
output_formatNoOutput format for all images (default: png)png

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The description discloses that generation occurs 'in parallel', which is a key behavioral trait. However, without annotations, it omits details on concurrency limits, error behavior, or cost implications, leaving some gaps.

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?

The description is a single, efficient sentence with no superfluous information, earning high marks for conciseness.

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 the presence of an output schema and 100% parameter coverage, the description sufficiently covers the core purpose and parallel behavior. It lacks depth on limitations or prerequisites but is adequate for the tool's complexity.

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%, so the description adds minimal value beyond what the schema provides. It does clarify the batch nature of the 'prompts' parameter but does not add new semantics.

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 clearly states the verb 'generate', the resource 'images', and specifies 'multiple' and 'in parallel from a list of prompts'. This distinguishes it from single-image generation tools like generate_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?

The description implies use for batch generation from multiple prompts, which is distinct from single prompt tools. However, it does not explicitly state when to use this over alternatives or provide any exclusions.

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/Tehnolabs/pixelforge-mcp'

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