Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_rollback

Restore a backup of a profile-owned extension and confirm the loaded version matches the expected one, so you can revert a broken extension update in a paired Chrome profile.

Instructions

Restore an artifact backup of a profile-owned extension and verify the 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>",
      "backup_id": "<backup_id>",
      "expected_version": "<expected_version>"
    },
    "name": "profile_helper_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes
profile_idYes
extension_idYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful behaviors beyond the name: it mutates state by overwriting the loaded extension from a backup, and it verifies against an expected version. It omits what happens on version mismatch, whether the rollback is aborted or forced, and whether permissions beyond profile ownership are needed.

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, stating the action and the verification step. It is efficient, though splitting the restore action from the verification clause would make the two phases easier to parse.

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 four-parameter mutation tool with zero schema coverage, no annotations, and no output schema, the description is too thin. It does not state the result of the verification step, what happens when expected_version does not match, or whether the restored extension is reloaded automatically.

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 0%, so all four parameters are undocumented in the schema. The description implies meaning for backup_id (which backup), profile_id/extension_id (scoping to a profile-owned extension), and expected_version (a verification target rather than an input to the restore), but gives no formats or identifier conventions.

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+resource pair: restoring an artifact backup of a profile-owned extension, plus a verification of the loaded version. That is concrete enough to distinguish it from preparation or staging helpers, though it never explicitly contrasts itself with the sibling profile_rollback or profile_backup.

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?

Use is only implied by the phrase 'Restore an artifact backup', which suggests recovery after a bad state. There is no statement of when to prefer this over profile_rollback or profile_helper_reconcile, and no prerequisites (such as a prior backup) are called out.

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