Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: metrics

cws_metrics
Read-onlyIdempotent

Retrieve daily Chrome Web Store metrics for an extension—installs, uninstalls, active users, impressions, and page views—optionally split by country, OS, version, language, or acquisition source.

Instructions

Read-only. Daily metrics of your item: installs, uninstalls, daily and 7-day active users, store impressions and detail-page views, optionally split by one dimension (country, OS, version, language, install source, UTM fields).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "metrics": "<metrics>"
    },
    "name": "cws_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD.
fromNoFirst date, YYYY-MM-DD.
itemIdNoThe 32-letter item ID. Defaults to CWS_ITEM_ID.
metricsYesWhich metrics to return.
pageSizeNoAt most this many rows (default 100).
dimensionNoSplit the rows by this (at most one).
pageTokenNonextPageToken from the previous page.
publisherIdNoYour publisher ID. Defaults to CWS_PUBLISHER_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The leading 'Read-only.' restates what readOnlyHint/destructiveHint already declare, earning little credit. Beyond annotations it adds useful substance — that data is daily-granularity and that rows can be split by exactly one dimension — but says nothing about pagination behavior, default date window, or how empty ranges behave.

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?

Two tight sentences with the resource and metric list front-loaded; no filler. The only waste is the opening 'Read-only.', which duplicates the annotation rather than adding information.

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 an 8-parameter read tool with full schema coverage and no output schema, the description covers what the tool returns and how dimension splitting works, which is the essential shape. The remaining gap — date-range defaults, paging expectations, and result row structure — is partly absorbed by the well-documented schema.

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 metric names and dimension choices ('country, OS, version, language, install source, UTM fields') and the at-most-one-dimension constraint, but adds no format, default, or interaction detail beyond the schema.

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 names a specific resource (daily metrics of your item) and enumerates the exact measures returned: installs, uninstalls, daily and 7-day active users, impressions, detail-page views. It is immediately distinguishable from siblings like cws_reviews or cws_item_status by resource, though it never explicitly contrasts with them.

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

Usage Guidelines3/5

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

Usage is only implied: it tells you a dimension can optionally split rows and that at most one is allowed, which guides how to call it. It gives no guidance on when to prefer this over sibling tools, no prerequisites (auth/publisher scope), and no note about default date ranges or pagination workflow.

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