Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_history

Retrieve chronological change-only observations for a Chrome Web Store item to track updates over time. Provide item id plus optional date range and limit.

Instructions

Get Chrome Web Store item history. Returns chronological change-only observations for a Chrome Web Store item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesChrome Web Store item id
toNoInclusive end date, YYYY-MM-DD
fromNoInclusive start date, YYYY-MM-DD
limitNoMaximum points, default 365, max 1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It mentions 'chronological change-only observations' but does not disclose rate limits, authentication needs, error behavior, or the nature of the observations. Only basic operational context is given.

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?

Two sentences, front-loaded with the core purpose. Every phrase is informative with no redundancy. Highly concise.

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 simple list tool with no output schema, the description is adequate but lacks details about the observation format, pagination, or limits beyond the parameter 'limit'. It is minimally complete but could be enhanced.

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 covers all 4 parameters with descriptions. The description adds no additional meaning beyond 'chronological change-only observations'. Baseline 3 for high schema coverage, and no extra value from the description.

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 verb 'Get' and the resource 'Chrome Web Store item history', with 'chronological change-only observations' clarifying the output. However, it does not differentiate from siblings like datasets_chrome_extensions_changes, which may serve a similar purpose.

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?

No guidance on when to use this tool versus alternative tools (e.g., datasets_chrome_extensions_item for full item details). The description lacks any contextual hints for selection.

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