Skip to main content
Glama
freema

Firefox DevTools MCP

by freema

restart_firefox

Restart Firefox with custom configuration: binary path, environment variables, headless mode, or preferences. All open tabs are closed.

Instructions

Restart Firefox with different configuration. Allows changing binary path, environment variables, and other options. All current tabs will be closed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firefoxPathNoNew Firefox binary path (optional, keeps current if not specified)
profilePathNoFirefox profile path (optional, keeps current if not specified)
envNoNew environment variables in KEY=VALUE format (optional, e.g., ["MOZ_LOG=HTMLMediaElement:5", "MOZ_LOG_FILE=/tmp/ff.log"])
headlessNoRun in headless mode (optional, keeps current if not specified)
startUrlNoURL to navigate to after restart (optional, uses about:blank if not specified)
prefsNoFirefox preferences to set at startup. Values are auto-typed: true/false become booleans, integers become numbers, everything else is a string. Requires MOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1.
Behavior3/5

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

Discloses that all current tabs will be closed, which is a key behavioral trait. However, no annotations are provided, so description should cover more details like process effects or permissions, which are missing.

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?

Two concise sentences front-load the main action with no unnecessary words. Every sentence adds value.

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?

Covers the basics but lacks details on restart process, return values, or prerequisites. For a tool with 6 parameters and no output schema or annotations, more context would help an agent use it 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 descriptions already cover all 6 parameters thoroughly (100% coverage). The description adds no additional parameter-specific meaning beyond mentioning binary path and env variables.

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 it restarts Firefox with different configuration, specifying verb and resource. It distinguishes from sibling tools which perform different actions like clicking or navigating.

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 this tool versus alternatives, or when not to use it. Only states purpose without context on prerequisites or exclusions.

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/freema/firefox-devtools-mcp'

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