Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_backup

Back up a verified Chrome extension artifact to content-addressable storage while excluding profile and extension storage data.

Instructions

Back up verified extension artifact with CAS; excludes 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>",
      "expected_version": "<expected_version>"
    },
    "name": "profile_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idNo
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses two real traits — the artifact is 'verified' before backup and storage is content-addressed ('CAS') — but says nothing about permissions, idempotency, what happens when the version check fails, or whether an existing artifact is overwritten, which are the traits that matter for a mutation.

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?

One front-loaded sentence with no filler, but the terseness borders on under-specification given the semantic load the schema leaves undocumented. Nothing is redundant; a little more content would have been earned.

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?

A mutation tool with three undocumented parameters, no output schema and no annotations cannot be adequately covered by a single clause. The failure mode implied by the required expected_version parameter and the optional extension_id are both left for the caller to guess.

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 three parameters, so the description must compensate and does not. It never explains that expected_version is an optimistic-concurrency token, nor why extension_id is optional while profile_id is required — the two most consequential ambiguities for correct invocation.

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 ('Back up verified extension artifact') and adds a scoping clause ('excludes profile and extension storage') that separates it from the profile-level backup siblings. It stops short of naming the closest alternative (profile_helper_backup), so an agent still has to reason about which backup surface to use.

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: the exclusion of profile and extension storage indirectly suggests that profile-level backups belong to another tool, but no sibling is named and no explicit when-to-use or when-not-to-use condition is stated. An agent can infer the scope from the description but receives no routing guidance.

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