Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chromewebstore_item

Fetch detailed Chrome Web Store extension or theme data by ID, including ratings, users, version, size, languages, developer, category, screenshots, and privacy links.

Instructions

Retrieve Chrome Web Store item details. Returns detail for a Chrome Web Store extension or theme, including name, rating, rating count, user count, version, last-updated date, size, supported languages, developer, category, screenshots, and privacy links. Defaults: country=us, lang=en.

Input Schema

NameRequiredDescriptionDefault
idYesChrome Web Store item id (32-character extension/theme id)
langNoTwo-letter language code
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose the read-only nature via 'Retrieve', the full set of returned fields, and the default storefront/language values that shape the response. It omits auth requirements, rate limits, and error behavior, which keeps it short of a 5 but well above baseline.

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?

Three sentences, front-loaded with the purpose before the return details and defaults. The long field enumeration is justified because there is no output schema, so it is not wasted space.

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 get-by-id tool with no output schema, the description fills the return-value gap by listing the fields returned and documents the defaults. The remaining omissions (invalid-id behavior, auth) are minor for a read-only lookup.

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 schema already documents all three parameters and the baseline is 3. The description adds value by stating the default values (`country=us`, `lang=en`), which the schema does not provide, giving the agent concrete defaults to reason about.

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 a specific verb (Retrieve) and resource (Chrome Web Store item details), and scopes it to a single extension/theme rather than a list. It is clear what the tool does, but it never differentiates itself from siblings such as chromewebstore_search, chromewebstore_charts, chromewebstore_reviews, or chromewebstore_privacy, so an agent must still infer the routing.

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: the tool takes a required `id`, so an agent can infer it is a get-by-id lookup rather than a search. There is no explicit when-to-use, when-not-to-use, or pointer to the search/sibling tools (e.g. to first find an id or to fetch reviews/permissions separately), leaving real guidance gaps.

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