Skip to main content
Glama
thenavidm

Firefly MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Expand image

generative_expand

Expand images beyond original borders by generating new pixels with Adobe Firefly, returning output URLs or an async job.

Instructions

Expand image. Consumes Firefly Services credits. Returns Adobe output URLs. Set wait=false to return an async job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoCompatibility alias for numVariations. Do not supply both.
maskNoMask image which will be used to expand the given image.
sizeNoThe desired width and height for the final expanded image in pixels. The maximum size for the output images is 3999px by 3999px.
waitNoWait for completion, default true. Set false to return the job immediately.
imageNoThe image to expand. Use a URL or an uploadID as the source for the image. Firefly only allows these listed domains for input URLs in the request: amazonaws.com windows.net dropboxusercontent.com storage.googleapis.com .
seedsNoArray of seed image IDs. These reference images help ensure consistent image generation across multiple API calls. For example, you can use the same seed to generate a similar image with different styles. If specified along with numVariations, the number of seeds must equal numVariations.
widthNoCompatibility alias: provide together with height instead of size.
heightNoCompatibility alias: provide together with width instead of size.
promptNoAn optional text prompt up to 1024 characters. The longer the prompt the better Firefly performs.
confirmNoMust be true to spend Firefly Services credits for the operation the user requested.
maskUrlNoCompatibility URL alias for mask.source.url.
downloadNoDownload completed media to FIREFLY_OUTPUT_DIR, default false. Requires wait=true.
imageUrlNoCompatibility URL alias for image.source.url.
placementNoThe position of the source image after Firefly resizes it. The value describes the horizontal and vertical placement and dimensions of the image in the output. Note you cannot use placement for source images when you also apply a mask image.
numVariationsNoGenerate this number of variations. numVariations defaults to the number of seed images, or to 1 if you do not specify seeds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotation coverage exists (readOnlyHint=false, openWorldHint=true, idempotentHint=false), but the description adds genuinely useful context beyond them: that the call consumes paid Firefly Services credits, that it returns Adobe-hosted output URLs, and that wait=false switches to async job semantics. It stops short of noting the credit-spend confirmation requirement or the relationship between async jobs and get_job_status.

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?

Three short, front-loaded sentences with no filler; purpose, cost, return shape, and async switch appear in order of importance. Its terseness is close to under-specification rather than padding, which is preferable.

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 15-parameter tool with nested objects and no output schema, mentioning the Adobe output URLs is a helpful return-value cue. However, it omits the required source image, the credit-confirmation flag, the deprecated image.mask property, and the multiple compatibility aliases, leaving real gaps an agent must discover in the schema.

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 description coverage is 100% and every one of the 15 parameters is documented in the schema, including aliases, deprecations, and domain restrictions, so the baseline is 3. The description's only parameter-level addition (wait=false → async) merely restates the schema's own text for wait.

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?

States a specific verb and resource ('Expand image'), which is unambiguous about the core operation. It does not differentiate from the sibling generative_fill, which performs a closely related filling/extending operation, so an agent cannot tell the two apart from the description alone.

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?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as generative_fill or the composite tools. The only conditional ('Set wait=false to return an async job') is invocation syntax, not usage guidance.

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

Deploy Server

Other Tools