Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_search

Search the Chrome Web Store dataset. Searches stored Chrome Web Store item snapshots. Item type enum: extension, theme, app, unknown.

Instructions

Search the Chrome Web Store dataset. Searches stored Chrome Web Store item snapshots. Item type enum: extension, theme, app, unknown. Sort enum: relevance, users_desc, rating_desc, reviews_desc, updated_desc, trending_desc. Status enum: active, removed. Manifest version enum: 2, 3. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query, max 256 characters
pageNoPage number, default 1
sortNoSort enum: relevance, users_desc, rating_desc, reviews_desc, updated_desc, trending_desc
statusNoStatus enum: active, removed
categoryNoExact Chrome Web Store category
developerNoExact displayed developer name
item_typeNoItem type enum: extension, theme, app, unknown
min_usersNoMinimum displayed user count
page_sizeNoPage size, default 20, max 100
min_ratingNoMinimum rating, 0 through 5
permissionNoExact declared permission
collects_dataNoFilter by public data-collection disclosure
developer_emailNoExact disclosed developer email
manifest_versionNoManifest version enum: 2, 3
min_rating_countNoMinimum rating count
has_broad_host_accessNoFilter by broad host access

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.5
    • addedInput schema / properties / item_type / enum
      Added value: +[
+  "extension",
+  "theme",
+  "app",
+  "unknown"
+]
    • addedInput schema / properties / manifest_version / enum
      Added value: +[
+  2,
+  3
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "users_desc",
+  "rating_desc",
+  "reviews_desc",
+  "updated_desc",
+  "trending_desc"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "active",
+  "removed"
+]
  2. Addedv1.5.0

TDQS

B3.1/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 behavioral burden, and it does disclose the credit-based billing model (1 credit/record, minimum 2, 100 per full page), which is genuinely useful cost context. However, it omits return format, pagination behavior beyond the schema, rate limits, and auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and billing, which is good, but four sentences are spent re-listing enum values already fully documented in the schema. Those lines do not earn their place, inflating the text without adding information.

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?

For a 16-parameter tool with no annotations and no output schema, the description covers the important cost dimension but leaves key gaps: it does not explain the result shape, how the many filters combine, or how it differs from sibling search/item/facets tools. Adequate but incomplete.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 16 parameters, setting the baseline at 3. The description merely repeats enum values (item_type, sort, status, manifest_version) that are already present in the schema, adding no meaning beyond what structured data provides.

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 ('Search the Chrome Web Store dataset') and clarifies the scope with 'stored Chrome Web Store item snapshots.' It does not, however, differentiate this tool from close siblings like datasets_chrome_extensions_item, datasets_chrome_extensions_facets, or chromewebstore_search, leaving the agent to infer the boundary.

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 explicit guidance on when to use this tool versus the many chrome-extension siblings, nor any exclusions or prerequisites. The enum listings describe filter values but do not tell the agent when this search is the right choice over item/facets/history tools.

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