Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_rollback

Restore a backed-up Chrome extension artifact to a paired profile with expected-version CAS validation and readback verification.

Instructions

Restore backed-up extension artifact with CAS and 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>",
      "backup_id": "<backup_id>",
      "expected_version": "<expected_version>"
    },
    "name": "profile_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes
profile_idYes
extension_idNo
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 provided, so the description carries the full burden of behavioral disclosure. It mentions 'CAS' and 'Chrome readback,' which hint at concurrency control and verification, but it does not explain permissions, side effects, what is overwritten, or what happens on failure.

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?

The description is a single front-loaded sentence with no wasted wording. It is concise, though the technical terms 'CAS' and 'Chrome readback' are compressed to the point of opacity.

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 rollback mutation tool with four parameters, no annotations, no output schema, and no schema descriptions. The one-sentence description is not complete enough to tell an agent how to call it safely or what behavior to expect.

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 input schema has four parameters with 0% description coverage, so the description must compensate. It only vaguely relates to backup_id via 'backed-up' and expected_version via 'CAS,' and it says nothing about profile_id or extension_id.

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 states a specific verb and resource: 'Restore backed-up extension artifact.' It clearly indicates a rollback operation, but it does not explicitly distinguish this tool from sibling tools such as profile_helper_rollback or profile_reconcile.

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 description implies the tool is used to restore a backup, but it gives no explicit when-to-use guidance, prerequisites, or alternatives. With many similar-sounding sibling tools, an agent is left to infer when this tool should be chosen over profile_helper_rollback or profile_reconcile.

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