Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_chrome_extensions_item

Retrieve a stored Chrome Web Store extension, theme, or app record by its 32-character ID to inspect name, category, users, rating, version, developer, permissions, privacy disclosures, and screenshots.

Instructions

Get a Chrome Web Store dataset item. Returns the stored record of one Chrome Web Store extension, theme or app by its 32-character id. It has name, item_type, category, users, rating, version, developer and disclosed email, declared permissions, host access flags, privacy disclosures and screenshots, taken from the latest observation.

Input Schema

NameRequiredDescriptionDefault
idYesChrome Web Store item id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the record comes from the latest observation, specifies the id is 32 characters, and lists the fields returned (name, item_type, category, etc.). It does not state error behavior or missing-item handling, but for a read-only get this is largely sufficient.

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 sentences, front-loaded with the core purpose, followed by a concise list of returned fields. The field list earns its place given the absence of an output schema. Some minor verbosity in the list, but overall efficient.

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?

For a simple get-by-id tool with full schema coverage and no output schema, the description explains what is returned and the id format. It is nearly complete; only minor gaps like error handling or how to source the id are missing, but those are usage concerns rather than description completeness issues.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% description coverage, so baseline is 3. The description adds meaning by specifying the id is '32-character', which is more precise than the schema’s 'Chrome Web Store item id' and helps validate input.

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?

States a specific verb ('Get') and resource ('Chrome Web Store dataset item'), and clarifies it returns a stored record from the latest observation. This distinguishes it from search/facets/metrics siblings, but it does not explicitly name an alternative like chromewebstore_item or datasets_chrome_extensions_search.

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 explicit guidance on when to use this tool versus alternatives such as chromewebstore_item (live version) or datasets_chrome_extensions_search. The need to supply an id is implied, but there is no mention of when-not to use it or how to obtain the id.

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