Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: roll back to an earlier version

cws_rollback
Destructive

Revert a Chrome Web Store extension to an earlier published version by publishing it under a new, higher version number. Use validateOnly to check the request first without changing anything.

Instructions

Write, asks the person first (unless validateOnly). Publishes an earlier package to all users under a new, higher version number. Use validateOnly to check the request without changing anything.

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": {
      "targetCrxVersion": "<targetCrxVersion>",
      "newVersion": "<newVersion>",
      "rollbackReason": "<rollbackReason>"
    },
    "name": "cws_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoThe 32-letter item ID. Defaults to CWS_ITEM_ID.
newVersionYesThe new version number it gets; must be higher than the current one.
publisherIdNoYour publisher ID. Defaults to CWS_PUBLISHER_ID.
validateOnlyNoOnly check the request; change nothing.
rollbackReasonYesWhy. Google keeps this for auditing and shows it in the dashboard.
targetCrxVersionYesThe earlier published version to go back to, e.g. 1.2.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds real value by explaining the surprising mechanic (old package shipped under a brand-new higher version) and the validateOnly branch, but says nothing about permissions, failure modes, or whether the rollback is reversible.

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?

Three short sentences, front-loaded with the write-and-confirm warning, then the core behavior, then the dry-run hint. Nothing is wasted, though the opening fragment 'Write, asks the person first' is clipped and slightly awkward.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter destructive write with full schema coverage and annotations carrying the safety hints, the description covers the key semantics of the rollback and the dry-run option. It lacks only operational detail (preconditions, error behavior), which is a minor gap given no output schema exists to explain.

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 100%, so every parameter is already documented, including the 'must be higher than current' constraint on newVersion and the audit purpose of rollbackReason. The description only restates validateOnly, adding no meaning beyond the schema; baseline 3 applies.

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: publishes an earlier package to all users, and explicitly notes it lands under a new, higher version number. The title adds the 'roll back' framing. It does not name a sibling (e.g. cws_publish vs cws_upload) for contrast, so a 4.

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?

The description implies when to use it (reverting to an earlier release) and explains the validateOnly dry-run path, but never states when to prefer cws_publish, cws_upload, or cws_cancel_submission instead, nor any prerequisite like an existing submission state.

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