Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_update

Update an installed Chrome extension from its profile-owned directory, backing up current files and verifying the loaded version matches the expected version.

Instructions

Update an extension installed from its profile-owned directory, backing up and verifying 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>",
      "stage_id": "<stage_id>",
      "expected_version": "<expected_version>"
    },
    "name": "profile_helper_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
stage_idYes
profile_idYes
expected_versionYes

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 behavioral burden. It does disclose two useful traits (a backup is taken and the loaded version is verified), which goes beyond a bare 'update'. But for a mutation with zero annotation coverage it leaves major questions open: required permissions, whether the extension must be unloaded first, whether a reload follows, what happens on version mismatch, and whether the operation is reversible.

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, and the key scoping condition (profile-owned directory) appears early. It is terse rather than padded, though the compression is part of why parameters and behavior go unexplained.

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?

This is a three-parameter mutation tool with no annotations and no output schema, so the description is the only source of behavioral and parameter context. It covers the action at a high level but leaves all three parameter semantics and most mutation side effects undocumented, which is not enough for an agent to call it confidently.

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%, so the description must explain the three required parameters, and it explains none of them explicitly. 'Verifying loaded version' loosely gestures at expected_version, but profile_id and stage_id get no meaning at all, and the optimistic-concurrency semantics of expected_version are never spelled out.

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 names a specific verb (update) plus a narrowly scoped resource: an extension installed from its profile-owned directory, and adds that it backs up and verifies the loaded version. That is more specific than a bare 'update'. It does not, however, distinguish this from siblings such as profile_update or profile_helper_stage, so the agent cannot tell which helper performs which step.

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 no explicit when-to-use guidance, no prerequisites, and no named alternative. The phrase 'backing up and verifying loaded version' hints that this is the safe update path versus profile_helper_stage or profile_helper_rollback, but the reader must infer that, and nothing states when this tool should be chosen over those siblings.

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