Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

chromewebstore_suggest

Generate Chrome Web Store search-term suggestions from a prefix, returning up to a set number of distinct item names for a chosen country and language.

Instructions

Suggest Chrome Web Store search terms. Returns search-term suggestions for a Chrome Web Store prefix given in term, up to num (default 8), with country and lang defaulting to us and en. Suggestions are the distinct item names of the top store-search results for that prefix, each returned as a term.

Input Schema

NameRequiredDescriptionDefault
numNoMaximum number of suggestions
langNoTwo-letter language code
termYesSearch prefix to autocomplete
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 burden, and it does add useful context beyond the schema: default values (num=8, country=us, lang=en) and a clear explanation that suggestions are the distinct item names of the top store-search results. It does not explicitly state read-only/non-mutating nature, but the suggest semantics make the operation's character clear.

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 sentences, front-loaded with the verb+resource, followed by parameters/defaults/return shape. Slight redundancy between 'Suggest ... search terms' and 'Returns search-term suggestions ...', but no wasted content.

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?

No output schema exists, so explaining the return value matters, and the description does so ('each returned as a term'). Parameters and defaults are covered. Only the usage context (when this beats chromewebstore_search) is absent, which is a minor gap for a simple read tool.

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 description coverage is 100%, so the baseline is 3, but the description adds the actual default values for num, country, and lang, which the schema does not convey. That is meaningful semantics beyond the schema.

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 and resource ('Suggest Chrome Web Store search terms') and clarifies the semantics as prefix-based autocomplete returning distinct item names from top store-search results. This is distinguishable from a full store search, but no sibling tool is named to make the contrast explicit.

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 phrase 'for a Chrome Web Store prefix' signals a typeahead/autocomplete scenario. There is no explicit when-to-use, when-not-to-use, or pointer to chromewebstore_search for full results.

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