Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chromewebstore_reviews

Fetch Chrome Web Store item reviews by extension or theme ID, returning author, star rating, review text, posted/edited dates, and reviewed version; set country, language, sort, and count.

Instructions

Retrieve Chrome Web Store item reviews. Returns the reviews the store renders on an item's reviews page, each with author, star rating, text, posted/edited dates and reviewed version. Defaults: num=20, country=us, lang=en.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesChrome Web Store item id (32-character extension/theme id)
numNoMaximum number of reviews
langNoTwo-letter language code
sortNoReview sort order
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "recent",
+  "helpful"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does well by disclosing the returned review fields (author, star rating, text, dates, reviewed version) and the default values for num, country, and lang. It does not mention pagination or rate limits, but this is a low-risk read operation and the core behavior is clear.

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 no filler. The purpose is front-loaded, and the return composition and defaults are packed efficiently into the second sentence without redundancy.

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?

With no output schema, the description supplies the essential return fields, and the schema fully documents the parameters. It is complete enough for an agent to call the tool correctly, though a bit more detail on sort behavior or result shape would make it stronger.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by stating default values for num, country, and lang, which helps an agent know what happens when these optional parameters are omitted.

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 uses a specific verb and resource: 'Retrieve Chrome Web Store item reviews.' It further clarifies scope by saying these are the reviews the store renders on an item's reviews page, which distinguishes it from related Chromewebstore tools like chromewebstore_item or chromewebstore_search.

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 gives clear context that this tool is for fetching the reviews shown on a specific item's store page, and id is required. It does not explicitly name alternatives or when-not-to-use conditions, but no sibling appears to compete directly for this purpose.

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

Deploy Server

Other Tools