Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: submit for review / publish

cws_publish
Destructive

Submits the current Chrome Web Store draft for review, then handles staged or default publication after approval with optional rollout percentage and review-skip settings.

Instructions

Write, asks the person first. Submits the current draft for review. STAGED_PUBLISH (default) waits after approval until the owner presses Publish; DEFAULT_PUBLISH goes live as soon as it is approved.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cws_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoThe 32-letter item ID. Defaults to CWS_ITEM_ID.
skipReviewNoAsk Google to skip review (only some updates qualify).
publishTypeNoSTAGED_PUBLISH
publisherIdNoYour publisher ID. Defaults to CWS_PUBLISHER_ID.
blockOnWarningsNoFail instead of submitting when Google reports warnings.
deployPercentageNoInitial rollout percentage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the risk profile is clear. The description adds context that those annotations do not cover: the operation is a write that asks the person first (human confirmation), and the staged mode defers the actual release until the owner acts. It omits any mention of rate limits or the effect on an existing pending submission.

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?

Two compact sentences that front-load the action and then explain the mode choice. The leading fragment 'Write, asks the person first' is slightly telegraphic and reads like a truncated note, but the remainder wastes no words.

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?

There is no output schema, so the description should cover behavior; it does so for mode semantics and the confirmation requirement. With six optional parameters already well documented in the schema, the remaining gap is minor: the qualifiers for skipReview ('only some updates qualify') are left to the schema, and return/result behavior is unspecified.

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 coverage is 83%, so the schema carries most parameter meaning. The description adds real value where the schema is silent: publishType has no per-value description in the schema, and the description explains what both enum values cause after approval. The other five parameters (itemId, publisherId, skipReview, blockOnWarnings, deployPercentage) are covered only by the schema.

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: it submits the current draft for review and can take it live. It clearly distinguishes the two publish modes, but it does not contrast itself with siblings such as cws_upload (which must precede it) or cws_cancel_submission (the way to stop a pending review).

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 guidance for the two modes is explicit: STAGED_PUBLISH is the default that waits for an owner-triggered Publish, while DEFAULT_PUBLISH goes live on approval. However, the description does not tell an agent when to choose this tool over cws_upload or cws_cancel_submission, or under what conditions a publish attempt is appropriate.

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