Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_extension_set_enabled

Enable or disable a Chrome extension in a paired existing profile and return Chrome readback to confirm the change.

Instructions

Enable or disable an extension in a paired existing profile and return Chrome readback

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>",
      "extension_id": "<extension_id>",
      "enabled": "<enabled>"
    },
    "name": "profile_extension_set_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
profile_idYes
extension_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden for a mutation tool, and it only adds the phrase 'return Chrome readback' as a hint about the response. It says nothing about whether the profile must be running, whether the change persists across reloads, what happens if the extension isn't installed, or whether the operation can fail or be rolled back.

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 the verb and scope first and the return-value note trailing. No filler, though 'Chrome readback' is jargon that costs a little clarity for a terse sentence.

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?

For a three-required-parameter mutation with no annotations, no output schema, and no parameter descriptions, the definition is thin. The only return-value signal is the vague phrase 'Chrome readback', leaving preconditions, side effects, and failure behavior undocumented.

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 coverage is 0%, so the description must compensate, and it partially does: it maps conceptually onto all three parameters (profile, extension, enable/disable toggle). However, it adds no format or validation detail for profile_id/extension_id that an agent couldn't already read from the schema, so it only narrowly clears the low-coverage bar.

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?

The description gives a specific verb pair (enable/disable), a named resource (extension) and a scope qualifier ('in a paired existing profile'), which is enough to distinguish it from read-only siblings like profile_extension_get and profile_extensions_list. It stops short of explicitly naming a sibling or stating what makes it different from, say, profile_reconcile or profile_helper_update.

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?

There is an implicit precondition ('paired existing profile'), which hints at when the tool is applicable, but no explicit when-to-use/when-not-to-use guidance and no routing to alternatives for installing, removing, or listing extensions. The agent must infer the boundary with siblings entirely on its own.

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