Skip to main content
Glama
chrome-store-mcp

chrome-store-mcp

by RayanBayat

Chrome Web Store: cancel the pending submission

cws_cancel_submission
Destructive

Cancels a Chrome Web Store submission that is awaiting review, with confirmation before applying the change.

Instructions

Write, asks the person first. Cancels the submission that is waiting for review.

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_cancel_submission"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new context: it is a write operation that 'asks the person first' (human confirmation required) and it only affects the submission awaiting review, not the published version. It does not elaborate on the non-idempotent behavior or what state remains after cancellation.

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 short sentences, front-loaded with the write/confirmation signal before the action itself. The fragment 'Write, asks the person first' is slightly telegraphic, but nothing is wasted.

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 two-optional-parameter tool with full schema coverage and explicit annotations, the definition covers the essentials: what is cancelled and that confirmation is required. It omits what happens after cancellation (e.g., whether the item reverts to a prior state or errors when no pending submission exists), which an agent would benefit from knowing.

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 already document their defaults (CWS_ITEM_ID, CWS_PUBLISHER_ID), so the description adds nothing about them. Baseline 3 is appropriate when the schema fully carries parameter meaning.

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 (cancels) and a precisely scoped resource ('the submission that is waiting for review'), which distinguishes it from siblings like cws_rollback or cws_publish that act on already-deployed versions. It does not explicitly name a sibling to contrast with, keeping it at 4 rather than 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?

The phrase 'the submission that is waiting for review' implies the precondition for use (a pending submission exists), but there is no explicit when-not guidance and no routing to alternatives such as cws_rollback for reverting a live version. Usage is inferable rather than stated.

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