Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: upload a new package

cws_upload
Destructive

Uploads a ZIP as the new draft package for an existing Chrome Web Store item, requiring a higher manifest version; nothing changes for users until published.

Instructions

Write. Uploads a ZIP as the new draft package of an existing item. Users see nothing until it is published. The manifest version must be higher than the last uploaded one. Creating a new item is not possible through the API.

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": {
      "zipPath": "<zipPath>"
    },
    "name": "cws_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoThe 32-letter item ID. Defaults to CWS_ITEM_ID.
zipPathYesAbsolute path to the extension ZIP.
publisherIdNoYour publisher ID. Defaults to CWS_PUBLISHER_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a destructive, non-idempotent, write operation, and the description adds real value beyond them: visibility semantics (nothing visible until published), the strictly-increasing manifest version requirement, and the inability to create items. It stops short of saying whether an existing draft is replaced or lost, which matters given destructiveHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the operation type and immediately followed by the constraints that affect a correct call. No filler or repetition of schema fields.

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 three-parameter mutation with no output schema and full annotation coverage, the definition covers purpose, side effects on end users, and the key precondition. Only the replacement behavior for an existing draft and any post-upload state details are absent.

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 100%, so itemId, zipPath, and publisherId are already fully documented, including environment-variable defaults and the ID pattern. The description adds no parameter-level detail, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource: uploads a ZIP as the new draft package of an existing item. It also scopes the operation (existing items only; creating new items is impossible via the API), which separates it from creation and from cws_publish.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames the upload as producing a draft that users will not see until published, and states the manifest-version prerequisite. It does not explicitly name cws_publish as the next step, but the draft-versus-published distinction supplies the operative context.

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