Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chromewebstore_charts

List Chrome Web Store top charts for trending, popular, or notable items by country and language, returning structured item cards with optional limits.

Instructions

List a Chrome Web Store top chart. Returns the item cards in a store top chart. chart accepts trending, popular, or notable. Defaults: chart=popular, num=50, country=us, lang=en.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoMaximum number of items
langNoTwo-letter language code
chartNoTop chart to list
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / chart / enum
      Added value: +[
+  "trending",
+  "popular",
+  "notable"
+]
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It communicates that this is a read-style operation (`List`, `Returns`) and exposes the valid chart values and defaults. However, it does not disclose the ordering of results, pagination behavior, or what an 'item card' actually contains, leaving non-trivial behavioral gaps for a tool without annotations.

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?

The description is compact and front-loaded with the core purpose, followed by a terse defaults line. The only waste is minor repetition: 'store top chart' appears in both the first and second sentences, and the second sentence could be merged with the first. Overall, every sentence earns its place.

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?

Given there is no output schema, the description's 'Returns the item cards' is too thin; an agent still does not know what fields an item card includes, how results are ordered, or whether pagination is available. The tool is simple and the defaults help, but the definition is not fully complete for an agent selecting this tool and interpreting its response.

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?

The input schema already covers 100% of parameters, so the baseline is 3. The description adds value beyond the schema by specifying concrete default values for all four parameters (`chart=popular`, `num=50`, `country=us`, `lang=en`) and restating the allowed chart values. This helps an agent know which parameters can be safely omitted.

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 states a specific verb and resource: 'List a Chrome Web Store top chart' and further scopes it by naming the accepted chart types (`trending`, `popular`, `notable`). The purpose is clear and distinct enough from siblings like chromewebstore_search or chromewebstore_similar, but it does not explicitly call out a sibling alternative, so it stops short of fully differentiating.

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 guidance on when to use this tool versus alternatives such as chromewebstore_search, chromewebstore_category, or chromewebstore_collection. The description provides defaults and valid chart values, which help invocation, but it never states the conditions that would route an agent to this tool instead of a sibling.

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