Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_metrics

Retrieve chart-ready Chrome Web Store dataset metrics, including coverage, adoption, ratings, permissions, privacy, and recent changes for 7, 30, or 90 days.

Instructions

Get Chrome Web Store dataset metrics. Returns chart-ready coverage, adoption, rating, permission, privacy and recent-change aggregates for the stored Chrome Web Store dataset. Days enum: 7, 30, 90.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoRecent-change window enum: 7, 30, 90; default 30
limitNoTop category and permission buckets, default 10, min 5, max 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / days / enum
      Added value: +[
+  7,
+  30,
+  90
+]
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions 'chart-ready' aggregates, which hints at output formatting, but does not describe side effects, rate limits, or the meaning of aggregates like 'coverage' or 'adoption'. It repeats the days enum from the schema without adding new behavioral context.

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?

The description is concise and front-loaded with the purpose. The inclusion of the days enum is redundant with the schema, but it does not significantly bloat the text. Overall it is efficient and to the point.

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 metrics tool with no output schema and no annotations, the description provides a reasonable overview of what it returns (aggregate categories) and the days parameter. It does not explain what each aggregate means or the exact output shape, but for a simple read-only metrics endpoint this is acceptable. More detail on output format would elevate completeness.

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% for both parameters (days and limit) with clear defaults and ranges. The description adds no new meaning beyond repeating the days enum, which is already in the schema. Per the rubric, baseline 3 is appropriate when the schema documents parameters well.

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 fetches Chrome Web Store dataset metrics and lists the aggregate categories (coverage, adoption, rating, permission, privacy, recent-change). This distinguishes it from sibling tools that handle search, item details, or history. It is not a tautology and uses a specific verb ('Get') and resource ('Chrome Web Store dataset metrics').

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 implies when to use it—when you need dataset-level aggregates—but does not explicitly state alternatives or conditions for not using it. Given the many sibling tools like datasets_chrome_extensions_search and datasets_chrome_extensions_item, clearer guidance on when to pick metrics over those would improve the score.

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