Skip to main content
Glama

deploy-percentage

Adjust the publish deploy percentage for staged rollouts on Chrome Web Store, enabling incremental updates to live users. Requires 10,000+ 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 async handler function that executes the deploy-percentage tool. Resolves item/publisher IDs, makes a POST request to the Chrome Web Store API endpoint `:setPublishedDeployPercentage` with the desired percentage, and formats the response.
      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,
          };
        }
      },
    );
  • Input schema for the deploy-percentage tool: validates `percentage` (0-100 number), optional `itemId` (string), and optional `publisherId` (string).
    {
      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')"),
    },
  • src/index.ts:410-448 (registration)
    Registration of the 'deploy-percentage' tool with the MCP server via `server.tool()`, including its description, input schema, and handler.
    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,
          };
        }
      },
    );
  • Helper function `resolveItemId` used to resolve the item ID from the parameter or fall back to the CWS_ITEM_ID environment variable.
    function resolveItemId(itemId?: string): string {
      const id = itemId || DEFAULT_ITEM_ID;
      if (!id) {
        throw new Error(
          "No item ID provided. Pass itemId parameter or set CWS_ITEM_ID env var.",
        );
      }
      return id;
    }
  • Helper function `resolvePublisherId` used to resolve the publisher ID from the parameter or fall back to the CWS_PUBLISHER_ID env var (or 'me').
    function resolvePublisherId(publisherId?: string): string {
      return publisherId || PUBLISHER_ID;
    }
Behavior3/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 discloses important constraints (incremental percentage, user count requirement) but omits behavioral details such as success/failure responses or whether the change triggers a publish. The description is moderately transparent but lacks depth.

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 concise: two sentences, no filler. It is front-loaded with the core action and follows with necessary constraints. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 3 parameters with full schema coverage, no output schema, and no annotations. The description covers the core action and constraints but lacks information about return values, error conditions, or post-effect behavior. For a simple mutation tool, it is adequate but not complete.

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%, and the description repeats the constraint from the schema ('Must be larger than the current target percentage'). It adds the default behavior for itemId and publisherId, but overall does not significantly enhance understanding beyond the schema with 3 parameters.

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 action: 'Set the published deploy percentage for staged rollout on Chrome Web Store.' It uses a specific verb ('Set') and identifies the resource ('deploy percentage'), differentiating it from siblings like 'cancel' or '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?

The description provides explicit conditions: the new percentage must be higher than the current target, and the tool is only available for items with 10,000+ seven-day active users. However, it does not explicitly mention when not to use this tool or suggest 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