Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_update_notification_destination

Update an eBay notification destination to modify its name, status, or HTTPS delivery endpoint using its unique destination ID.

Instructions

Update a notification destination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDestination name
statusNoStatus: ENABLED or DISABLED
destinationIdYesThe unique identifier for the destination
deliveryConfigNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.14.1
    • addedInput schema / properties / deliveryConfig
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "endpoint": {
+      "description": "HTTPS endpoint URL",
+      "format": "uri",
+      "type": "string"
+    },
+    "verificationToken": {
+      "description": "Verification token (32-80 alphanumeric, underscore, hyphen characters)",
+      "maxLength": 80,
+      "minLength": 32,
+      "pattern": "^[a-zA-Z0-9_-]+$",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / delivery_config
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Delivery configuration",
-  "properties": {
-    "endpoint": {
-      "description": "HTTPS endpoint URL",
-      "type": "string"
-    },
-    "verification_token": {
-      "description": "Verification token (32-80 characters)",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / destinationId
      Added value: +{
+  "description": "The unique identifier for the destination",
+  "type": "string"
+}
    • removedInput schema / properties / destination_id
      Removed value: -{
-  "description": "The unique identifier for the destination",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "destination_id"
-]New value: +[
+  "destinationId"
+]
  2. First observedv1.8.10

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention idempotency, partial updates, or required permissions. The tool is mutative, but no side effects or constraints are described.

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 extremely concise, consisting of a single sentence. While it is not verbose, it may be too brief to be helpful, but it does follow the principle of being 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?

Given the tool has four parameters including a nested object, no output schema, and no annotations, the description is insufficient. It does not explain the effect of updating each field or the response behavior, leaving the agent with limited information.

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 high at 75%, so the input schema already documents most parameters. The description adds no additional meaning beyond 'update'. For properties like 'deliveryConfig', the schema includes detailed descriptions, so the marginal value of the description is minimal.

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 verb 'Update' and resource 'notification destination', providing a straightforward purpose. However, it does not differentiate from sibling tools like ebay_update_notification_config or ebay_update_notification_subscription, which are also 'Update' operations on notifications.

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 is provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, such as needing a destinationId, or when to update vs. create/delete destinations.

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

Deploy Server

Other Tools