Amazon Selling Central MCP

Feeds_cancelFeed

Cancel a specified Amazon Selling Partner feed to stop processing when it's no longer needed or was submitted with errors. Provide the feed identifier to prevent unwanted updates.

Instructions

Catalog entry. Runs in your Kuudo deployment, not here. Cancels the feed that you specify.

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": "Feeds_cancelFeed"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the behavioral burden. It discloses the primary effect ('Cancels the feed') and the execution location ('in your Kuudo deployment, not here'), but says nothing about side effects, reversibility, required permissions, or response behavior. For a mutating operation, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the opening 'Catalog entry' is filler and the execution-location note is placed before the actual purpose. It is concise but structurally awkward, with the core operation stated last rather than front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool lacks an output schema, annotations, and a usable parameter schema. Critical details such as how to specify the feed, what success looks like, and what states allow cancellation are missing. The 'Kuudo deployment' note adds one useful context signal but does not compensate for the absent operational guidance.

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

Parameters2/5

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

The input schema is empty with additionalProperties true, so the schema provides no parameter meaning. The description adds only 'the feed that you specify' without naming a parameter or format. An agent is told that a feed must be identified, but not how to provide that identifier in an API call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Cancels the feed that you specify.' It clearly communicates the operation and is distinguishable from sibling Feeds tools like Feeds_createFeed, Feeds_getFeed, and Feeds_createFeedDocument because it is the cancel action.

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 when-to-use guidance is provided. It does not say when cancellation is appropriate, whether feeds can only be cancelled in a certain status, or what prerequisites exist. The only usage signal is derived from the tool name itself, which the description does not meaningfully expand on.

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

Deploy Server