Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: item status

cws_item_status
Read-onlyIdempotent

Inspect a Chrome Web Store item's review and publication state, including revisions, versions, rollout percentages, policy warnings, takedown status, and last upload state. Read-only.

Instructions

Read-only. Review and publication state of your item: published and submitted revisions (PENDING_REVIEW, STAGED, PUBLISHED, REJECTED...), their versions and rollout percentages, policy warnings, takedown, and the last upload state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cws_item_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdNoThe 32-letter item ID. Defaults to CWS_ITEM_ID.
publisherIdNoYour publisher ID. Defaults to CWS_PUBLISHER_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered and 'Read-only' merely repeats it. What the description adds beyond that is substantive: since there is no output schema, its enumeration of the revision states, rollout percentages, policy warnings and takedown is the only signal about what the call actually returns.

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?

Two sentences, front-loaded with the safety qualifier and then the returned-state inventory; no filler. Slightly dense but every clause maps to a real piece of returned information.

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?

With no output schema, this description carries the return-value burden and does it well by listing the publish/rollout/policy dimensions. Minor gaps remain around auth requirements and behavior when the item is missing or the defaults are unset, but nothing critical for correct invocation is absent.

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 coverage is 100% and both parameters (itemId pattern, publisherId pattern, env-var defaults) are fully documented in the schema itself. The description adds no further meaning about these parameters, so baseline 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 gives a specific read operation over a named resource ('review and publication state of your item') and enumerates the observable values (PENDING_REVIEW, STAGED, PUBLISHED, REJECTED, rollout percentages, policy warnings, takedown, last upload state), which makes it easy to tell apart from the mutation-oriented siblings like cws_publish or cws_rollback. It never explicitly names a sibling, so it falls short of a 5.

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?

'Read-only' plus the status-focused framing implies the agent should call this to check state, but there is no explicit when-to-use/when-not statement, no mention of prerequisites, and no routing to alternatives such as cws_metrics or cws_reviews for other data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.