Skip to main content
Glama

list_extensions

Read-only

Lists installed Firefox extensions, with optional filtering by exact ID, partial name, or active status, to inspect browser add-ons.

Instructions

List installed Firefox extensions using the WebDriver BiDi webExtension.moz:listExtensions command.

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": "list_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoOptional: Filter by exact extension IDs (e.g., ["addon@example.com"])
nameNoOptional: Filter by partial name match (case-insensitive, e.g., "shopify")
isActiveNoOptional: Filter by enabled (true) or disabled (false) status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.11.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description carries a lower burden. The mention of the underlying webExtension.moz:listExtensions command adds minor technical context, but the description says nothing about error behavior, empty results, or whether an active session is required.

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?

A single front-loaded sentence with no filler, which is well matched to a simple read tool. The trailing protocol-command clause adds little practical value for an agent selecting or invoking the tool.

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?

With three optional, fully documented parameters and a readOnly annotation, the description is close to adequate. However, no output schema exists, so the description could have said what a listing returns (e.g., extension IDs, names, active state), and that gap leaves the agent guessing about the response shape.

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%, and each of the three filters (ids, name, isActive) is documented in the schema with examples, so the description correctly defers to the schema. It adds no meaning of its own about how filters combine or whether they are ANDed.

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 and resource ("List installed Firefox extensions") that an agent can immediately distinguish from the mutation sibling install_extension. However, it never names an alternative or clarifies scope such as whether it only returns extensions installed in the current session versus all profiles.

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

Usage Guidelines3/5

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

Usage is only implied by the verb "list"; there is no explicit statement of when to call this versus install_extension, nor any prerequisite such as an active Firefox session or BiDi capability. An agent can infer the read-only retrieval case, but nothing is spelled out.

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