Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_search

Search stored Chrome Web Store snapshots to find extensions, themes, and apps by query, category, developer, rating, users, permissions, or manifest version.

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.

Input Schema

TableJSON 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

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It doesn't mention pagination, default page size, whether results are snapshots or live, how filters combine, or any side effects. The tool is likely read-only but this isn't stated. The description adds no behavioral context beyond listing enums.

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 short (three sentences) but redundant, listing enums that are already defined in the input schema. This repetition wastes space without adding value. It front-loads the purpose, but the enumeration is unnecessary, making it less concise than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters, no output schema, and no annotations, the description is inadequate. It does not explain pagination behavior, result structure, default sort/status, or how multiple filters combine. An agent has no idea what to expect from the call, making the tool hard to use correctly.

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 coverage is 100%, so the baseline is 3. The description repeats enum values already in the schema without adding extra meaning or clarifying how parameters interact. It does not compensate for the schema's lack of context on defaults or combinations, but it doesn't need to since the schema is complete.

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 clearly states the tool searches the Chrome Web Store dataset, using a specific verb ('Search') and resource ('Chrome Web Store dataset'). It distinguishes from non-search tools but does not differentiate from sibling search tools like datasets_chrome_extensions_facets or datasets_chrome_extensions_item. It's clear but not uniquely positioned.

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?

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites or typical use cases. With many sibling dataset tools, an agent cannot tell if this is the right choice without further context.

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