Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_notification_subscription

Retrieve a specific eBay notification subscription by its unique ID. Get subscription details to verify configuration and status.

Instructions

Get a specific notification subscription by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesThe unique identifier for the subscription

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.14.1
    • 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

B3.2/5.0
Behavior2/5

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

No annotations provided; description only states basic function. Does not disclose authentication needs, error behavior, or that this is a read-only operation. Burden falls on description, but it fails to add behavioral context.

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?

Description is a single sentence with no wasted words. Concise and to the point, though it could include more context 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?

For a simple getter with one parameter and no output schema, the description is adequate but lacks behavioral transparency and usage guidelines. It is minimally complete.

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 100% for the single parameter. Description does not add meaning beyond schema; baseline score of 3 applies.

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?

Description clearly states the verb 'Get' and resource 'notification subscription by ID'. It distinguishes from sibling tools like ebay_get_notification_subscriptions (list all) by specifying 'by ID'.

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 guidelines on when to use this tool or when to use alternatives. Among many notification subscription siblings, context is missing to help an agent choose correctly.

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