Skip to main content
Glama
Sign In
adobe-firefly-mcp

adobe-firefly-mcp

by peroxide-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Adobe Firefly Generate

firefly_generate

Send an image prompt to Adobe Firefly, with optional control over style, aspect ratio, content class, and negative prompt. Requires prior manual Adobe sign-in.

Instructions

Generate images in Adobe Firefly using the existing persistent browser session. Requires manual Adobe sign-in in the browser profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "firefly_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMaximum number of generated images to save.
styleNoOptional visible Firefly style/control label to try to select.
promptYesImage prompt to send to Adobe Firefly.
outputDirNoOptional output directory. Relative paths resolve under the MCP data dir.
aspectRatioNoOptional Firefly aspect ratio label, such as "1:1" or "16:9".
contentClassNoOptional Firefly content type/control label, such as "Photo" or "Art".
negativePromptNoOptional things to avoid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions the sign-in requirement but omits critical details such as potential side effects, error behavior, rate limits, or what happens to the browser session. This lack of transparency leaves significant gaps for an agent.

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?

The description is extremely concise: two sentences that immediately convey the core action and a critical prerequisite. Every word serves a purpose, and the most important information is front-loaded. No redundancy or fluff.

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?

Despite having 7 parameters and no output schema, the description fails to explain what the tool returns, how errors are handled, how to effectively use optional parameters, or any post-invocation behavior. For a complex image generation tool, this is insufficient, leaving the agent without essential operational context.

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?

The input schema already provides complete descriptions for all 7 parameters (100% coverage). The tool description does not add meaningful semantic context beyond what the schema already conveys, so it meets the baseline of 3 but does not excel.

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?

The description clearly states the verb 'Generate' and the resource 'images in Adobe Firefly', and it uniquely identifies the tool among siblings by distinguishing it from video generation or background removal. It also specifies the context of a persistent browser session, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly notes the prerequisite of manual Adobe sign-in and the use of an existing persistent browser session, providing clear context for when to use the tool. However, it does not offer exclusion criteria or alternatives (e.g., comparing with firefly_generate_video), so it falls short of a perfect score.

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