Skip to main content
Glama

create-visual

Generate images from text, edit existing visuals, or search for inspiration on the web and academic papers. Supports standard sizes and formats.

Instructions

Create, edit, or search for visual content. Supports three modes: generate (create images from text), edit (modify existing images), and search (find visual inspiration from the web). Note: Supported image sizes are 1024x1024, 1536x1024, 1024x1536, or auto - custom sizes like 512x512 are not available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesOperation mode: generate new images, edit existing images, or search for visual inspiration
promptYesText description of the desired visual or search query
modelNoImage model to use (generate/edit modes only)
sizeNoImage dimensions (generate/edit modes only). IMPORTANT: Only these sizes are supported by the GPT Image API. Other sizes like 512x512 are not available. Use 1024x1024 for square images.
qualityNoRendering quality (generate/edit modes only)
backgroundNoBackground transparency (generate/edit modes only)
outputFormatNoOutput image format (generate/edit modes only)
outputCompressionNoCompression level for JPEG/WebP (generate/edit modes only)
partialImagesNoNumber of partial images for streaming (generate/edit modes only)
nNoNumber of images to generate (generate/edit modes only)
inputImagesNoInput images as base64 strings or file IDs (edit mode only)
inputImageMaskNoOptional mask image for inpainting (edit mode only)
inputFidelityNoInput image detail preservation level (edit mode only)
searchModeNoSearch domain: web or academic papers (search mode only)
searchRecencyFilterNoFilter results by recency (search mode only)
Behavior3/5

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

With no annotations, the description carries the burden. It discloses supported image sizes but lacks information on destructive actions, authentication, rate limits, or return value format.

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?

Two concise sentences covering purpose and a critical constraint. Could be slightly improved by front-loading mode selection guidance.

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

Completeness2/5

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

For a tool with 15 parameters and no output schema, the description is too brief. It does not explain return values, workflow, or how modes differ in input/output.

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 has 100% description coverage with detailed parameter explanations. The description's additional note about size constraints is redundant with the schema's own 'IMPORTANT' note.

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 the tool creates, edits, or searches for visual content using three specific modes. This distinguishes it from sibling tools that focus on consulting, copy improvement, or problem-solving.

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

Usage Guidelines3/5

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

Description implies when to use each mode but does not explicitly contrast with alternatives like 'search-content'. No guidance on when not to use this tool.

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/effatico/kortx-mcp'

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