Skip to main content
Glama

publish

Publish Chrome Web Store extensions with options for immediate release, staged rollouts, or skipping review when eligible.

Instructions

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

Input Schema

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

Implementation Reference

  • The 'publish' tool implementation handles Chrome Web Store extension publishing by calling the Google API. It parses parameters, prepares the JSON payload for publish settings, and executes the API call.
    server.tool(
      "publish",
      "Publish an extension to Chrome Web Store. Supports immediate publish, staged publish, initial deploy percentage, and skip-review.",
      {
        itemId: z
          .string()
          .optional()
          .describe("Extension item ID (defaults to CWS_ITEM_ID env var)"),
        publisherId: z
          .string()
          .optional()
          .describe("Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')"),
        publishType: z
          .enum(["DEFAULT_PUBLISH", "STAGED_PUBLISH"])
          .optional()
          .describe(
            "DEFAULT_PUBLISH: publishes immediately after approval. STAGED_PUBLISH: stages for manual publishing after approval. Defaults to DEFAULT_PUBLISH."
          ),
        deployPercentage: z
          .number()
          .int()
          .min(0)
          .max(100)
          .optional()
          .describe("Initial deploy percentage for staged rollout (0-100). Only used with STAGED_PUBLISH or DEFAULT_PUBLISH."),
        skipReview: z
          .boolean()
          .optional()
          .describe("Attempt to skip review if the extension qualifies. Defaults to false."),
      },
      async ({ itemId, publisherId, publishType, deployPercentage, skipReview }) => {
        try {
          const id = resolveItemId(itemId);
          const pub = resolvePublisherId(publisherId);
    
          const url = `${API_BASE}/v2/publishers/${pub}/items/${id}:publish`;
    
          const body: Record<string, unknown> = {};
          if (publishType) body.publishType = publishType;
          if (deployPercentage !== undefined) {
            body.deployInfos = [{ deployPercentage }];
          }
          if (skipReview !== undefined) body.skipReview = skipReview;
    
          const hasBody = Object.keys(body).length > 0;
    
          const result = await apiCall(url, {
            method: "POST",
            ...(hasBody
              ? {
                  headers: { "Content-Type": "application/json" },
                  body: JSON.stringify(body),
                }
              : {}),
          });
    
          return formatResponse(result);
        } catch (e: any) {
          return {
            content: [{ type: "text" as const, text: `Error: ${e.message}` }],
            isError: true,
          };
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions behavioral aspects like 'immediate publish' and 'skip-review', but fails to disclose critical traits such as required permissions, rate limits, whether the action is reversible (e.g., via 'cancel'), or what happens on failure. This leaves significant gaps for a mutation tool.

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?

The description is a single, dense sentence with zero waste—every phrase ('immediate publish', 'staged publish', etc.) directly informs the tool's capabilities. It is front-loaded with the core purpose and efficiently lists key features without redundancy.

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?

Given the complexity of a publish operation with 5 parameters, no annotations, and no output schema, the description is incomplete. It omits essential context such as success/failure outcomes, error handling, side effects (e.g., impact on extension status), and how it integrates with sibling tools like 'status' or 'cancel'.

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 fully documents all 5 parameters. The description adds minimal value beyond the schema by hinting at parameter usage (e.g., 'initial deploy percentage' for 'deployPercentage'), but does not provide additional context like default behaviors or interdependencies beyond what's in the schema descriptions.

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?

The description clearly states the specific action ('Publish an extension to Chrome Web Store') and resource ('extension'), distinguishing it from siblings like 'upload' (which likely uploads files) or 'update-metadata' (which modifies metadata). It provides precise scope by mentioning supported features like immediate/staged publishing and skip-review.

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 lacks explicit guidance on when to use this tool versus alternatives. It mentions features like staged publishing but does not clarify prerequisites (e.g., after uploading an extension), exclusions (e.g., not for updates), or direct comparisons to siblings like 'deploy-percentage' or 'update-metadata'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/cws-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server