Skip to main content
Glama
mikusnuz

cws-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

publish

Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.

Instructions

Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.

Input Schema

NameRequiredDescriptionDefault
itemIdNoExtension item ID (defaults to CWS_ITEM_ID env var)
skipReviewNoAttempt to skip review if the extension qualifies. Defaults to false.
publishTypeNoDEFAULT_PUBLISH: publishes immediately after approval. STAGED_PUBLISH: stages for manual publishing after approval. Defaults to DEFAULT_PUBLISH.
publisherIdNoPublisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')
blockOnWarningsNoReject publishing when validation returns warnings (default: false)
deployPercentageNoInitial deploy percentage for staged rollout (0-100). Only used with STAGED_PUBLISH or DEFAULT_PUBLISH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.2
    • addedInput schema / properties / blockOnWarnings
      Added value: +{
+  "description": "Reject publishing when validation returns warnings (default: false)",
+  "type": "boolean"
+}
  2. First observedv1.4.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral burden. It does not explain whether publishing is irreversible, what review or approval flow occurs, what permissions are required, how warnings are handled, or what happens on failure.

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?

The description is two short clauses, front-loaded with the core action and resource. It is efficient, though it could optionally add one clarifying sentence about the publish workflow without becoming verbose.

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?

This is a no-annotation mutation tool with no output schema and six optional parameters, yet the description does not cover authorization, defaults from environment variables, review behavior, or the result of publishing. The schema covers parameter details, but behavioral context is substantially missing.

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 the schema already documents all six parameters. The description adds only a high-level mapping to publishType, deployPercentage, and skipReview, while omitting itemId, publisherId, and blockOnWarnings context.

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: 'Publish an extension to Chrome Web Store.' It also names publish modes, but it does not explicitly distinguish this tool from siblings such as upload, deploy-percentage, or cancel.

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?

The description lists supported modes ('immediate publish, staged publish, initial deploy percentage, and skip-review') but gives no guidance on when to choose publish versus upload, deploy-percentage, or cancel. There are no explicit exclusions or preconditions.

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

Deploy Server

Other Tools