Skip to main content
Glama

update-metadata

Modify Chrome Web Store listing metadata including title, description, category, and URLs using the v1.1 API. Supports both standard fields and advanced custom metadata.

Instructions

Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports both common fields and raw metadata payload for advanced fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026. Use update-metadata-ui as an alternative.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdNoExtension item ID (defaults to CWS_ITEM_ID env var)
titleNoStore listing title
summaryNoStore listing short summary
descriptionNoStore listing description
categoryNoCategory (e.g. 'productivity', 'developer_tools')
defaultLocaleNoDefault locale (e.g. 'ko', 'en')
homepageUrlNoHomepage URL
supportUrlNoSupport URL
metadataNoRaw metadata object forwarded as-is to the v1 API. Useful for fields not exposed as first-class params.

Implementation Reference

  • The handler function for the update-metadata tool, which builds a payload from input parameters and calls the API.
    async ({
      itemId,
      title,
      summary,
      description,
      category,
      defaultLocale,
      homepageUrl,
      supportUrl,
      metadata,
    }) => {
      try {
        const id = resolveItemId(itemId);
        const url = `${V1_BASE}/items/${id}`;
    
        const payload: Record<string, unknown> = {
          ...(metadata || {}),
        };
        if (title !== undefined) payload.title = title;
        if (summary !== undefined) payload.summary = summary;
        if (description !== undefined) payload.description = description;
        if (category !== undefined) payload.category = category;
        if (defaultLocale !== undefined) payload.defaultLocale = defaultLocale;
        if (homepageUrl !== undefined) payload.homepageUrl = homepageUrl;
        if (supportUrl !== undefined) payload.supportUrl = supportUrl;
    
        if (Object.keys(payload).length === 0) {
          throw new Error("No metadata fields provided.");
        }
    
        const result = await apiCall(url, {
          method: "PUT",
          headers: { "Content-Type": "application/json" },
          body: JSON.stringify(payload),
        });
    
        return formatResponse(result);
      } catch (e: any) {
        return {
          content: [{ type: "text" as const, text: `Error: ${e.message}` }],
          isError: true,
        };
      }
    },
  • The Zod schema defining the input parameters for the update-metadata tool.
    {
      itemId: z
        .string()
        .optional()
        .describe("Extension item ID (defaults to CWS_ITEM_ID env var)"),
      title: z
        .string()
        .optional()
        .describe("Store listing title"),
      summary: z
        .string()
        .optional()
        .describe("Store listing short summary"),
      description: z
        .string()
        .optional()
        .describe("Store listing description"),
      category: z
        .string()
        .optional()
        .describe("Category (e.g. 'productivity', 'developer_tools')"),
      defaultLocale: z
        .string()
        .optional()
        .describe("Default locale (e.g. 'ko', 'en')"),
      homepageUrl: z
        .string()
        .optional()
        .describe("Homepage URL"),
      supportUrl: z
        .string()
        .optional()
        .describe("Support URL"),
      metadata: z
        .record(z.unknown())
        .optional()
        .describe(
          "Raw metadata object forwarded as-is to the v1 API. Useful for fields not exposed as first-class params."
        ),
    },
  • src/index.ts:479-481 (registration)
    The registration of the update-metadata tool using the server.tool method.
    server.tool(
      "update-metadata",
      "Update the store listing metadata of a Chrome Web Store item (v1.1 API). Supports both common fields and raw metadata payload for advanced fields. Note: v1 API is deprecated and will be removed after Oct 15, 2026. Use update-metadata-ui as an alternative.",
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions the API version and deprecation timeline, which is useful context, but doesn't disclose permissions needed, rate limits, whether changes are reversible, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

Three sentences with zero waste: first states purpose and capabilities, second notes deprecation, third gives alternative. Each sentence earns its place by adding critical information, and it's appropriately front-loaded with the core functionality.

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?

For a mutation tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It covers purpose and usage guidelines well but lacks behavioral details like permissions, side effects, or response format. The high schema coverage helps, but more context is needed for safe and effective use.

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 9 parameters thoroughly. The description adds value by explaining that it 'Supports both common fields and raw metadata payload for advanced fields,' which clarifies the dual approach, but doesn't provide additional syntax or format details beyond what the schema provides.

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 ('Update'), resource ('store listing metadata of a Chrome Web Store item'), and API version ('v1.1 API'). It distinguishes from sibling 'update-metadata-ui' by mentioning it as an alternative, showing differentiation.

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 provides when-not-to-use guidance ('v1 API is deprecated and will be removed after Oct 15, 2026') and names a specific alternative ('Use update-metadata-ui as an alternative'). This gives clear context for tool selection.

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