Fetch a Chrome Web Store extension, theme, or legacy app snapshot by its 32-character item ID, returning the stored listing record.
Get a Chrome Web Store dataset item. Returns one stored extension, theme or legacy app snapshot by its 32-character Chrome Web Store id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Chrome Web Store item id |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It indicates the operation is read-only (returns a snapshot) and specifies the id format. However, it lacks details on authentication, error handling, or data freshness. Basic behavioral info is present but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that conveys all essential information without unnecessary words. It is front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description adequately covers what it does and what it returns. It mentions the type of returned items (extension, theme, app snapshot) and the id format. Minor gap: no mention of error behavior or response structure, but overall sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The parameter id is described in the schema as 'Chrome Web Store item id'. The description adds the constraint that the id is 32 characters, which clarifies the format beyond the schema's generic description. This provides useful additional context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets a Chrome Web Store dataset item, and specifies it returns one stored extension, theme, or legacy app snapshot by its 32-character id. This differentiates it from sibling tools like search or changes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when a specific 32-character id is known, but does not explicitly state when to use this tool versus alternatives (e.g., search or other datasets tools). No exclusions or prerequisites are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.