Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_trending

Find trending Chrome Web Store extensions, themes, and apps ranked by recent user and rating-count changes, with filters for category, developer, permissions, and data collection.

Instructions

Get trending Chrome Web Store items. Returns stored Chrome Web Store items ranked by the latest observed user and rating-count movement. Filters match the search endpoint; sort is fixed to trending_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query
pageNoPage number
statusNoStatus enum: active, removed
categoryNoExact category
developerNoExact developer
item_typeNoItem type enum: extension, theme, app, unknown
min_usersNoMinimum users
page_sizeNoPage size, max 100
min_ratingNoMinimum rating
permissionNoExact permission
collects_dataNoData-collection filter
developer_emailNoExact developer email
manifest_versionNoManifest version enum: 2, 3
min_rating_countNoMinimum rating count
has_broad_host_accessNoBroad-host-access filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / status / enum
      Added value: +[
+  "active",
+  "removed"
+]
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It reveals the ordering logic and fixed sort, which is relevant. However, it omits other behavioral traits such as pagination behavior, default result size, data freshness, and read-only expectations, so transparency is adequate but incomplete.

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

Conciseness5/5

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

The description is compact: two sentences, no filler, and the core action is front-loaded. Every sentence contributes either the ranking rationale or the filter/sort compatibility note.

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 tool with 15 optional parameters, no annotations, and no output schema, the description gives a reasonable but incomplete picture. It explains the ranking and fixed sort but leaves return value shape, pagination defaults, and explicit sibling-tool routing unstated.

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 schema already documents all 15 parameters and the baseline is 3. The description adds a useful aggregate note that these filters match the search endpoint, but it does not enrich individual parameter meanings 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?

The description opens with a specific verb and resource: 'Get trending Chrome Web Store items.' It also clarifies the ranking basis ('latest observed user and rating-count movement'), which makes the tool's purpose clear. It does not explicitly name or differentiate sibling tools, so it stops short of a 5.

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?

The description gives useful context: filters map to the search endpoint and sort is fixed to 'trending_desc'. However, it never explicitly states when to choose this tool over alternatives like datasets_chrome_extensions_search or datasets_chrome_extensions_history, leaving the routing decision to inference.

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