Skip to main content
Glama
thenavidm

Firefly MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Generate images

generate_image

Generate images from text prompts using Adobe Firefly Services. Returns Adobe output URLs, supports async jobs, and consumes credits.

Instructions

Generate images. 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.
sizeNoThe desired width and height for the final image, in pixels. Supported sizes for the output images with `image3` are: Square (1:1) - width 2048px, height 2048px Square (1:1) - width 1024px, height 1024px Landscape (4:3) - width 2304px, height 1792px Portrait (3:4) - width 1792px, height 2304px Widescreen (16:9) - width 2688px, height 1536px Widescreen (16:9) - width 2688px, height 1512px (7:4) - width 1344px, height 768px (7:4) - width 1344px, height 756px (9:7) - width 1152px, height 896px (7:9) - width 896px, height 1152px Supported sizes for the output images with `image4` are: (1:1) - width 2048px, height 2048px (4:3) - width 2304px, height 1792px (3:4) - width 1792px, height 2304px (16:9) - width 2688px, height 1536px (9:16) - width 1440px, height 2560px .
waitNoWait for completion, default true. Set false to return the job immediately.
seedsNoAn array of seed image IDs. These reference images help ensure consistent image generation across multiple API calls. For example, use the same seed to generate a similar image in different styles. If specified along with numVariations, the number of seeds provided must equal numVariations.
styleNoAn object with the reference image details for style.
widthNoCompatibility alias: provide together with height instead of size.
heightNoCompatibility alias: provide together with width instead of size.
promptYesA text prompt to support the generation of an image. The longer the prompt the better Firefly performs.
confirmNoMust be true to spend Firefly Services credits for the operation the user requested.
downloadNoDownload completed media to FIREFLY_OUTPUT_DIR, default false. Requires wait=true.
structureNoAn object with the reference image details for structure.
contentClassNoDirects the style of a generated image to be photographic or like fine art.
customModelIdNoInclude the specific custom model ID when a custom model type is designated in the `x-model-version` header parameter.
numVariationsNoThe number of variations to generate. numVariations defaults to the number of seed images, or to 1 if you do not specify `seeds`.
upsamplerTypeNoOnly supported with the model version `image4_custom`. The `default` setting upscales generated images to 2k. The `low_creativity` setting refines the image generation by removing distortions, smoothing textures, and sometimes adding details (like freckles to faces in close-up). This setting is recommended for generating images with human subjects.default
negativePromptNoA negative prompt of things Firefly will try to avoid generating in the image. Not supported for Firefly Custom Models on Image Model 3 or Firefly Custom Models on Image Model 4.
visualIntensityNoAdjust the overall intensity of your photo's characteristics, such as contrast, shadow, and hue. This is not supported with the model version `image4_custom`.
promptBiasingLocaleCodeNoA hyphen-separated string combining the ISO 639-1 language code and the ISO 3166-1 region (like en-US). When a locale is set, the prompt will be biased to generate more relevant content for that region. If not specified, the locale will be auto-detected based on your profile and the accepted language header.

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?

Annotations cover the safety profile (readOnly=false, destructive=false, openWorld=true, idempotent=false), and the description adds genuinely new context: it consumes Firefly Services credits, returns Adobe output URLs, and supports an async path via wait=false. It does not mention the confirm flag requirement for spending credits, which is a notable omission for a cost-incurring tool.

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?

Four short, front-loaded sentences with no filler; purpose comes first, followed by cost, output, and the async toggle. Tight and readable, though the async note duplicates the schema.

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 an 18-parameter tool with nested objects and no output schema, the description is thin: it does not explain the credit-confirmation flow (confirm=true), the download-to-directory path, or how job results are retrieved. The rich schema compensates somewhat, but the async workflow is only half-described.

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%, so all 18 parameters are already documented in the schema, making 3 the baseline. The description only adds the wait=false async behavior, which the schema already states, so it contributes little param-level meaning.

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 clear verb+resource (generate images) so the agent knows exactly what it produces. However, it offers no differentiation from close siblings like generate_image5, generate_similar, or generate_video, which an agent must choose between.

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?

The only usage guidance is 'Set wait=false to return an async job,' which is a mode toggle rather than when-to-use-this-tool guidance. There is no mention of when to prefer this over generate_image5, generate_similar, or the composite tools.

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