Skip to main content
Glama

Adobe Firefly Variations

firefly_variations

Upload a local image and generate multiple variations with optional prompt, aspect ratio, and count, saving results to a directory.

Instructions

Upload a local image to Adobe Firefly and create variations through the persistent browser session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoMaximum images to save.
promptNoOptional prompt or direction for the variation.
imagePathYesLocal source image path. Relative paths resolve from the server cwd.
outputDirNoOptional output directory.
aspectRatioNoOptional visible aspect ratio label.
Behavior2/5

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

Mentions 'persistent browser session' hinting at statefulness, but no discussion of side effects, authentication needs, error handling, or return behavior. With no annotations, description inadequately discloses behavioral traits.

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

Conciseness5/5

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

Single sentence, front-loaded with essential action, no redundant words.

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?

High parameter count (5) and no output schema leave gaps. Description does not explain return values, non-required parameter interactions, or error states. Insufficient for agent to use correctly.

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%; description adds no extra meaning beyond schema. Baseline of 3 applies as no additional parameter context is provided.

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?

Clearly states verb 'Upload' and resource 'local image to Adobe Firefly' with outcome 'create variations'. Distinguishes from siblings like firefly_generate (generate from scratch) and firefly_expand (expand).

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 vs. alternatives like firefly_generate or prerequisites like needing a browser session. Agent lacks context for selection.

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/peroxide-dev/adobe-firefly-mcp'

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