Set up an eBay notification destination by configuring a name, HTTPS endpoint, and verification token to receive event alerts.
Create a notification destination
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Seller-specified name for the destination | |
| status | No | Status: ENABLED or DISABLED | |
| deliveryConfig | No |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / deliveryConfigAdded 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"
+}Input schema / properties / delivery_configRemoved value: -{
- "additionalProperties": false,
- "description": "Delivery configuration with endpoint and verification token",
- "properties": {
- "endpoint": {
- "description": "HTTPS endpoint URL (no internal IPs or localhost)",
- "format": "uri",
- "type": "string"
- },
- "verification_token": {
- "description": "Verification token (32-80 alphanumeric, underscore, hyphen characters)",
- "maxLength": 80,
- "minLength": 32,
- "pattern": "^[a-zA-Z0-9_-]+$",
- "type": "string"
- }
- },
- "type": "object"
-}v1.12.0Input schema / properties / delivery_configAdded value: +{
+ "additionalProperties": false,
+ "description": "Delivery configuration with endpoint and verification token",
+ "properties": {
+ "endpoint": {
+ "description": "HTTPS endpoint URL (no internal IPs or localhost)",
+ "format": "uri",
+ "type": "string"
+ },
+ "verification_token": {
+ "description": "Verification token (32-80 alphanumeric, underscore, hyphen characters)",
+ "maxLength": 80,
+ "minLength": 32,
+ "pattern": "^[a-zA-Z0-9_-]+$",
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Input schema / properties / destinationRemoved value: -{
- "additionalProperties": true,
- "description": "Destination configuration",
- "properties": {
- "endpoint": {
- "type": "string"
- },
- "name": {
- "type": "string"
- },
- "verificationToken": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "endpoint"
- ],
- "type": "object"
-}Input schema / properties / nameAdded value: +{
+ "description": "Seller-specified name for the destination",
+ "type": "string"
+}Input schema / properties / statusAdded value: +{
+ "description": "Status: ENABLED or DISABLED",
+ "type": "string"
+}Input schema / requiredRemoved value: -[
- "destination"
-]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Create', but does not describe side effects, whether verification is needed, or what happens upon successful creation. The schema includes a verification token, but this is not mentioned in the description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise at one sentence, but it sacrifices necessary information. While concise, it does not earn its place as it provides no value beyond the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (nested input object, no output schema, no annotations), the description is insufficient. It does not explain what a notification destination is, what the response contains, or how to verify creation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has descriptions for all parameters (name, status, deliveryConfig with nested fields), so schema coverage is high. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Create a notification destination', which clearly indicates the verb (create) and resource (notification destination). However, it does not differentiate from sibling tools that also create other resources (e.g., ebay_create_notification_subscription, ebay_create_report_task), so it lacks specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. There is no mention of prerequisites, required prior steps (e.g., setting up an endpoint), or how it relates to notifications and subscriptions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.