adobe-firefly-mcp

by peroxide-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Adobe Firefly DOM Inspector

firefly_dom_inspect

Inspect Adobe Firefly DOM state to diagnose broken automation, discover CSS selectors, and explore shadow DOM.

Instructions

Inspect the current Adobe Firefly DOM state for debugging. This is a read-only tool that never navigates, clicks, or modifies the page. Use it to diagnose broken automation, discover selectors, and inspect shadow DOM.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firefly_dom_inspect"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Inspection mode	full
`maxDepth`	No	Maximum depth for tree/shadow traversal
`selector`	No	CSS selector for selector mode (required when mode=selector)
`includeHtml`	No	Save HTML snapshot to debug/dom.html
`includeConsole`	No	Capture console messages
`includeNetwork`	No	Capture network requests
`includeScreenshot`	No	Save screenshot to debug/dom-inspect.png
`maxConsoleMessages`	No	Maximum console messages to return
`maxNetworkRequests`	No	Maximum network requests to return
`includeAccessibility`	No	Include accessibility tree
`captureElementScreenshots`	No	Save individual screenshots for each discovered element
`includeAnnotatedScreenshot`	No	Save annotated screenshot with element labels

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description fully carries the burden and delivers: 'This is a read-only tool that never navigates, clicks, or modifies the page.' This is a model of behavioral transparency, clearly stating safety guarantees. Additional context about inspecting shadow DOM and discovering selectors adds value.

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 two concise sentences with no filler. The most critical information (purpose, read-only guarantee) is front-loaded. Every sentence serves a purpose.

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?

Given the tool has 12 parameters, no output schema, and no annotations, the description provides a clear purpose and behavioral guarantee but lacks guidance on parameter interplay (e.g., which mode for which use case) and what the return value looks like. The description covers essential context but is incomplete for fully informed tool selection.

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 baseline is 3. The description does not add significant parameter-level detail beyond what the schema provides. It mentions some use cases (shadow DOM, selectors) that hint at parameter choices but does not elaborate on mode selection or other options.

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 'inspect', the resource 'Adobe Firefly DOM state', and the purpose 'for debugging'. It explicitly distinguishes itself as a read-only diagnostic tool, differentiating from sibling tools like firefly_dom_watch (likely for monitoring changes) and firefly_debug_bundle (a broader debug collection).

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 states when to use: 'Use it to diagnose broken automation, discover selectors, and inspect shadow DOM.' This provides clear context. However, it does not explicitly mention when not to use or compare with alternatives like firefly_dom_watch, leaving some ambiguity for agents deciding between tools.

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

Deploy Server