Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_changes

Track recent Chrome Web Store item changes by type—users, rating, version, developer, permissions, privacy, or status—and return up to 500 observations with changed figures.

Instructions

Get recent Chrome Web Store item changes. Lists recent change observations across Chrome Web Store items in the dataset, optionally for one change_type: users, rating, rating_count, version, developer, permissions, privacy or status. Returns up to limit (default 100, max 500), each with the item's name, category, developer, observed time and the figures that changed.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum observations, default 100, max 500
change_typeNoChange type enum: users, rating, rating_count, version, developer, permissions, privacy, status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / change_type / enum
      Added value: +[
+  "users",
+  "rating",
+  "rating_count",
+  "version",
+  "developer",
+  "permissions",
+  "privacy",
+  "status"
+]
  2. Addedv1.5.0

TDQS

B3.2/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 burden, and it does disclose return content (item name, category, developer, observed time, changed figures) plus the default and max of limit. It stops short of stating that it is a read-only operation, the ordering of results, or any auth/rate-limit behavior.

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?

Three compact sentences, front-loaded with the core action, then filtering, then return shape. Every sentence contributes; only minor tightening would be possible.

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?

There is no output schema, so the description correctly compensates by enumerating the returned fields, and it covers both optional parameters and their bounds. For a two-parameter read listing with no annotations, this is nearly complete, lacking only result ordering and explicit read-only framing.

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% and both parameters are already fully documented, including the enum values and the limit default/max. The description merely restates those facts, adding no syntax or semantic nuance beyond the schema, so the baseline of 3 applies.

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 recent Chrome Web Store item changes') and elaborates that it lists change observations, so the agent knows exactly what it produces. It does not name or contrast any sibling (e.g. datasets_chrome_extensions_history, datasets_chrome_extensions_item, datasets_chrome_extensions_metrics), so differentiation is left to inference.

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?

It states that the change_type filter is optional, which implies a general 'list all changes' use case, but gives no explicit when-to-use guidance, no prerequisites, and no comparison against the very similar chrome-extension siblings. The agent must guess when this beats history or item lookups.

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