Skip to main content
Glama

image_outpainting

Extend images beyond their borders using a mask and text prompt to generate new content in the extended area, with optional negative prompt and guidance scale.

Instructions

Outpaint / extend image beyond borders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of variations to generate.
promptYesText description of what to generate in the extended area.
mask_urlYesURL of the mask defining the region to extend into.
image_urlYesURL of the source image.
guidance_scaleNoHow closely to follow the prompt (higher = more literal).
negative_promptNoWhat to avoid in the generated content.
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It mentions 'extend image beyond borders', implying a mutation, but does not state whether this is destructive, requires authentication, or rate limits. Lacks transparency for a generative tool.

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

Conciseness3/5

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

The description is very short (5 words). While concise, it lacks structure—no sentences or additional context. It is minimally adequate but could be more informative without being verbose.

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?

Given 6 parameters, no output schema, and siblings that perform related tasks, the description is incomplete. It does not explain key details like the need for a mask and prompt, or how output differs from alternatives. Schema descriptions help, but tool-level context is missing.

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 all 6 parameters have descriptions. The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate; no improvement from description.

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 'Outpaint / extend image beyond borders' clearly indicates the tool's function: extending an image outward. It distinguishes from inpainting (filling inside), but among siblings like 'generative_fill', the distinction is implicit. Still, it's specific and understandable.

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?

No guidance on when to use this tool versus alternatives (e.g., 'magic_inpaint', 'generative_fill'). No when-not-to-use or prerequisites mentioned. The description is purely declarative with no usage context.

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/celeryhq/simplified-mcp-server'

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