Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chromewebstore_similar

Retrieve related Chrome Web Store items by 32-character ID and optional country/language, returning each card's name, publisher, category, rating, users, and URL.

Instructions

Retrieve related Chrome Web Store items. Returns the related-items shelf shown on a Chrome Web Store item's page. id is the required 32-character item id; country and lang default to us and en. Each card has name, publisher, category, rating, rating count, users, summary, icon and URL. An unknown or removed id returns 404.

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 behavioral burden and does well: it enumerates the returned fields (name, publisher, category, rating, rating count, users, summary, icon, URL) and discloses the 404 failure mode for unknown or removed ids. It omits auth requirements, rate limits, and result-count/pagination behavior.

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?

Four tight sentences, front-loaded with what the tool returns before diving into parameters and edge cases. Dense and free of filler, though the returned-fields enumeration is a slight run-on.

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 read-only lookup with no annotations and no output schema, the description covers purpose, inputs, defaults, return fields, and the primary failure mode. Only minor gaps remain (no mention of how many related items come back or ordering).

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, but the description adds real meaning beyond the schema: the id must be a 32-character item id, and country/lang default to us and en (defaults are not stated in the schema). This exceeds what the structured fields convey.

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 ('related Chrome Web Store items') and clarifies it surfaces the related-items shelf on an item's page. That distinguishes it in substance from chromewebstore_item and chromewebstore_search, though it never names a sibling explicitly.

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?

Implies the usage context (you need an item id and want its related shelf), and adds the error case for unknown/removed ids, but gives no explicit when-to-use vs. when-not guidance or alternative tools to consider.

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