Skip to main content
Glama

deploy-percentage

Set the published deploy percentage for staged rollout on Chrome Web Store. Increase the target percentage for extensions with 10,000+ seven-day active users.

Instructions

Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
percentageYesDeploy percentage (0-100). Must be larger than the current target percentage.
itemIdNoExtension item ID (defaults to CWS_ITEM_ID env var)
publisherIdNoPublisher ID (defaults to CWS_PUBLISHER_ID env var or 'me')

Implementation Reference

  • The handler implementation for the "deploy-percentage" tool which makes a POST request to the Chrome Web Store API to update the deploy percentage.
    server.tool(
      "deploy-percentage",
      "Set the published deploy percentage for staged rollout on Chrome Web Store. The new percentage must be higher than the current target. Only available for items with 10,000+ seven-day active users.",
      {
        percentage: z
          .number()
          .min(0)
          .max(100)
          .describe("Deploy percentage (0-100). Must be larger than the current target percentage."),
        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')"),
      },
      async ({ percentage, itemId, publisherId }) => {
        try {
          const id = resolveItemId(itemId);
          const pub = resolvePublisherId(publisherId);
    
          const url = `${API_BASE}/v2/publishers/${pub}/items/${id}:setPublishedDeployPercentage`;
          const result = await apiCall(url, {
            method: "POST",
            headers: { "Content-Type": "application/json" },
            body: JSON.stringify({ deployPercentage: percentage }),
          });
    
          return formatResponse(result);
        } catch (e: any) {
          return {
            content: [{ type: "text" as const, text: `Error: ${e.message}` }],
            isError: true,
          };
        }
      },
    );
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing critical behavioral constraints: the percentage increase requirement and the 10,000+ user prerequisite. It doesn't mention rate limits, authentication needs, or error behaviors, but provides substantial operational context.

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?

Two sentences with zero waste - first states the core purpose, second provides critical constraints. Perfectly front-loaded with the essential information first, no redundant or unnecessary phrasing.

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 mutation tool with no annotations and no output schema, the description provides strong context about prerequisites and constraints. It could benefit from mentioning what happens on success or typical response format, but covers the most critical operational aspects well.

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 baseline is 3. The description reinforces the percentage constraint but doesn't add meaningful semantic context beyond what's already in the schema descriptions for parameters like itemId and publisherId.

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 ('Set the published deploy percentage'), identifies the resource ('staged rollout on Chrome Web Store'), and distinguishes this from sibling tools like 'publish' or 'update-metadata' by focusing specifically on percentage-based rollout management.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('Only available for items with 10,000+ seven-day active users') and provides clear constraints ('The new percentage must be higher than the current target'), giving specific conditions for proper tool selection versus alternatives.

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