Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ebay_update_notification_subscription

Modify an eBay notification subscription by updating status, payload format, schema version, delivery protocol, or destination ID.

Instructions

Update a notification subscription

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoStatus: ENABLED or DISABLED
payloadNo
destinationIdNoThe unique identifier of the destination
subscriptionIdYesThe unique identifier for the subscription

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv1.14.1
    • addedInput schema / properties / destinationId
      Added value: +{
+  "description": "The unique identifier of the destination",
+  "type": "string"
+}
    • removedInput schema / properties / destination_id
      Removed value: -{
-  "description": "The destination endpoint ID",
-  "type": "string"
-}
    • removedInput schema / properties / payload / description
      Removed value: -"Payload configuration"
    • addedInput schema / properties / payload / properties / deliveryProtocol
      Added value: +{
+  "description": "Delivery protocol",
+  "type": "string"
+}
    • removedInput schema / properties / payload / properties / delivery_protocol
      Removed value: -{
-  "description": "Delivery protocol",
-  "type": "string"
-}
    • addedInput schema / properties / payload / properties / schemaVersion
      Added value: +{
+  "description": "Schema version for the notification topic",
+  "type": "string"
+}
    • removedInput schema / properties / payload / properties / schema_version
      Removed value: -{
-  "description": "Schema version",
-  "type": "string"
-}
    • addedInput schema / properties / subscriptionId
      Added value: +{
+  "description": "The unique identifier for the subscription",
+  "type": "string"
+}
    • removedInput schema / properties / subscription_id
      Removed value: -{
-  "description": "The unique identifier for the subscription",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "subscription_id"
-]New value: +[
+  "subscriptionId"
+]
  2. First observedv1.8.10

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states 'Update'. It fails to disclose whether mutations are partial or complete, required permissions, or side effects.

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 extremely concise at one sentence, but it sacrifices valuable details that could fit without becoming verbose. It is not optimally structured.

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?

Given no output schema, no annotations, and minimal description, the tool is under-documented. Important details like update semantics, valid values, and response behavior are missing.

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 75%, so the schema already documents most parameter meanings. The description adds no extra value beyond the schema's parameter descriptions.

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 clearly states the action ('Update') and the resource ('a notification subscription'). It is specific enough to understand the tool's core function, though it does not differentiate from sibling enable/disable tools.

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 guidance on when to use this tool versus alternatives like enable or disable subscriptions. The description lacks context on prerequisites or use cases.

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/YosefHayim/ebay-mcp'

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