Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_disable_notification_subscription

Stop receiving eBay notifications by disabling a subscription using its unique identifier.

Instructions

Disable a notification subscription

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_idYesThe unique identifier for the subscription
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Disable', implying a state change, but does not explain if the operation is reversible, what happens to the subscription's configuration, or any side effects. This is insufficient for a mutation tool.

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?

The description is a single, front-loaded sentence that conveys the core purpose without waste. It is concise, though it could benefit from slight expansion to improve clarity without becoming verbose.

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?

Given the single parameter and no output schema, the description provides minimal context. It does not explain return values, success indicators, or preconditions. For a simple disable action, it is somewhat adequate but lacks completeness for an AI agent.

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?

The schema has 1 parameter with 100% description coverage, so baseline is 3. The description adds no extra meaning beyond the schema; the parameter name and description are clear. The overall tool description does not elaborate on how to use the parameter in context.

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 'Disable a notification subscription' clearly states the action (disable) and the resource (notification subscription). It is specific and uses a strong verb. However, it does not differentiate from sibling tools like ebay_delete_notification_subscription or ebay_enable_notification_subscription, which could cause confusion.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context such as whether the subscription must be active before disabling. The agent receives no help in deciding between this and similar tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jyarbro/ebay-seller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server