Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_update

Update a controlled Chrome profile using compare-and-swap with an expected version to prevent conflicting changes.

Instructions

Update a controlled profile with CAS

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_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.6/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 disclosure burden, and it does almost none of it. "CAS" hints at optimistic concurrency and that a version mismatch can fail the call, but it never states what fields are modified, what happens on a stale expected_version, whether changes are staged or immediate, or what permissions 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 seven-word sentence with zero filler and the core mechanism front-loaded. It is efficient, though brevity here is under-specification as much as conciseness.

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 mutation tool with concurrency semantics, three required parameters, no annotations, and no output schema, this definition is far too thin. An agent could not reliably predict failure modes or what state the profile is left in after a successful call.

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 the description must compensate for three undocumented required parameters (profile_id, stage_id, expected_version). "CAS" at least implies expected_version is the compare token, but stage_id and profile_id receive no explanation and the schema says nothing about their format or relationship.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update a controlled profile with CAS" names a verb (update) and resource (profile) plus a mechanism (CAS), so the agent knows this is a mutation under optimistic concurrency. However, "controlled profile" is unexplained jargon and nothing distinguishes this from siblings like profile_helper_update or profile_stage, which read as near-synonyms.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as profile_stage, profile_rollback, or profile_reconcile. The agent must infer entirely from the name and "CAS" that this is the compare-and-swap path versus the helper path.

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