Skip to main content
Glama
Sign In
Firefly MCP Server

Firefly MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Upscale image

upscale_image

Increase image resolution by 2x, 3x, 4x, or 6x using Adobe Firefly, returning output URLs or an async job for further processing.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
waitNoWait for completion, default true. Set false to return the job immediately.
imageNoThe input image for the upsampler (source uploadId or url).
seedsYesThe seed for each variation. Provide one seed per output (1–4 seeds).
confirmNoSet true only when the user asked for exactly this action.
downloadNoDownload completed media to FIREFLY_OUTPUT_DIR, default false. Requires wait=true.
imageUrlNoCompatibility URL alias for image.source.url.
upscaleFactorNoThe upscale factor (2, 3, 4, or 6). Output dimensions are input dimensions multiplied by this factor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to spend Firefly Services credits for the operation the user requested."New value: +"Set true only when the user asked for exactly this action."
    • changedInput schema / properties / image / properties / source / properties / uploadId / format
      Previous value: -"uuid4"New value: +"uuid"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, open-world, non-idempotent, non-destructive), so the bar is lower. The description adds genuinely useful context beyond them: it consumes Firefly Services credits, it returns Adobe output URLs, and wait=false yields an async job — all things an agent needs to plan cost and flow.

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; cost, return value, and async behavior each get one line. The opening 'Upscale image' mildly restates the title, which is the only waste.

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?

With no output schema, the description usefully names the return shape (Adobe output URLs) and covers cost and async behavior. Remaining gaps are minor since the rich schema documents source URL domains, uploadId, seeds, and upscaleFactor.

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 seven parameters including the wait/download/upscaleFactor semantics are already documented. The description only restates the wait=false behavior and adds no new parameter meaning, so the baseline 3 applies.

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+resource ('Upscale image') that clearly separates it from sibling generators like generate_image or generative_fill. It does not explicitly name siblings or scope, but the action is unambiguous.

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 flag rather than a when-to-use rule. Nothing tells the agent when to pick this over generate_similar, generative_expand, or the other image siblings, nor any prerequisite conditions.

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