Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_backup

Back up a verified unpacked extension artifact from a paired Chrome profile while excluding profile and extension storage.

Instructions

Back up a verified unpacked extension artifact from a paired profile, excluding profile and extension storage

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_version": "<expected_version>"
    },
    "name": "profile_helper_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idYes
expected_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?

With no annotations, the description carries the full burden; it does disclose real behavioral scope by stating what is excluded (profile and extension storage) and that the artifact must be verified and the profile paired. It omits destination/persistence of the backup, overwrite behavior, whether it mutates state, and any permission or rate-limit constraints.

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 clause with no filler; the exclusion clause earns its place. It reads as a fragment, which slightly weakens immediate parseability but wastes no words.

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?

Three required parameters, zero schema documentation, no annotations, and no output schema leave the description responsible for far more than it delivers. It says nothing about where the backup lands, what success looks like, or failure modes such as an unverified artifact or mismatched expected_version.

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% for all three required parameters, so the description must compensate and largely does not. It hints at the concepts (paired profile, artifact, "expected" version implying a match check) but never explains what profile_id, extension_id, or expected_version mean, nor what happens on a version mismatch.

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?

Specific verb+resource: "Back up a verified unpacked extension artifact from a paired profile," with a scope clause excluding profile and extension storage. An agent can tell this is narrower than a full profile backup, though it never names profile_backup or other siblings explicitly.

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?

Usage is only implied through preconditions embedded in the phrasing ("verified" artifact, "paired" profile). There is no explicit when-to-use statement, no when-not, and no routing to alternatives such as profile_backup or profile_helper_stage.

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