Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_extensions_list

Lists installed extensions in a specified paired Chrome profile so you can inspect what is enabled before managing or troubleshooting it.

Instructions

List extensions in a paired existing 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": {
      "profile_id": "<profile_id>"
    },
    "name": "profile_extensions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about read-only safety, pagination, ordering, or what happens for an unpaired/unknown profile_id. "List" implies a read, but that is inferred rather than stated.

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, though its brevity edges toward under-specification rather than tightness. Nothing is wasted, but little is delivered.

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?

With no annotations and no output schema, the definition should describe what a returned extension entry looks like and any filtering or paging behavior; it does neither. For a simple one-parameter list tool the bar is low, but the description falls short of it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter profile_id is documented at 0% coverage in the schema, and the description only obliquely implies it ("in a paired existing profile"). It adds no information about the identifier's format, source, or validity constraints.

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 ("List") and resource ("extensions") scoped to a profile, which is enough to distinguish it from profile_extension_get (singular retrieval) and the profile_helper_* mutation tools. The qualifier "paired existing profile" is slightly opaque but still conveys the operation.

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?

The phrase "in a paired existing profile" gestures at a prerequisite (the profile must already be paired), but nothing states when to choose this over profile_extension_get or the profile_helper_* variants. No exclusions or alternatives are given.

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