Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_reload

Reloads an unpacked Chrome extension in a paired profile through its authorized debugging channel and verifies the loaded version matches the expected version.

Instructions

Reload in a paired existing profile using its explicitly authorized Chrome debugging channel; verify loaded version

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>",
      "expected_current_version": "<expected_current_version>",
      "expected_version": "<expected_version>"
    },
    "name": "profile_helper_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idYes
expected_versionYes
expected_current_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the transport (Chrome debugging channel) and that a version verification occurs after the reload, but it says nothing about side effects on a running browser, what happens on version mismatch, or permission failures.

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 compact sentence with the action front-loaded and no filler. The phrasing 'Reload in a paired existing profile' is slightly awkward, but nothing is wasted.

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?

Four required parameters at zero schema coverage, no output schema, and no annotations leave the description far too thin for a mutating reload-with-verification operation. It should at minimum define the two version parameters and the failure semantics.

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?

Schema description coverage is 0% across four required parameters, and the description only obliquely gestures at 'loaded version'. Critically, it never explains the distinction between expected_current_version and expected_version, which is the one thing an agent must get right to call this safely.

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 (Reload) and resource (profile) plus the mechanism (Chrome debugging channel) and a post-condition (verify loaded version). It does not, however, distinguish itself from the sibling profile_reload, so an agent cannot tell from the text which of the two to pick.

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?

Implies preconditions ('paired existing profile', 'explicitly authorized Chrome debugging channel') but never states when to use this versus profile_reload or the other profile_helper_* tools. Usage must be inferred from the name and the 'helper' framing.

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