Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: rating summary

cws_rating_summary
Read-onlyIdempotent

Fetch a Chrome Web Store item's rating summary—overall rating, star counts, and number of ratings containing review text—without modifying data.

Instructions

Read-only. Your item's store rating, the number of ratings for each star, and how many have review text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cws_rating_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoThe 32-letter item ID. Defaults to CWS_ITEM_ID.
publisherIdNoYour publisher ID. Defaults to CWS_PUBLISHER_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so 'Read-only.' merely repeats structured data. The description does add value by disclosing the returned content (rating, star histogram, review-text count), which the agent cannot get from annotations, but it says nothing about freshness, empty-state behavior, or failure modes for unpublished items.

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 short sentences, front-loaded with the useful content and carrying no filler. The leading 'Read-only.' is the one wasted sentence since annotations already establish it.

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 simple two-optional-parameter read tool with full schema coverage, the description covers the essential unknown — the shape of the returned summary — which matters because there is no output schema. It is slightly thin on defaults and empty results, but nothing an agent needs to invoke it is absent.

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 both parameters document their own patterns and environment-variable defaults, so baseline 3 applies. The description adds no meaning beyond the schema — it never mentions that both params are optional or how publisherId interacts with itemId.

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?

States concretely what is returned: the item's store rating, a per-star rating count, and how many ratings carry review text. That is specific enough to separate it from cws_reviews (individual reviews) without the agent opening a schema, though it never names that sibling to make the distinction explicit.

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?

There is no when-to-use guidance and no named alternative. The agent must infer that this is the aggregate companion to cws_reviews and that calling it with no itemId falls back to a default item. Nothing states prerequisites, such as whether the item must be published.

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