Retrieve eBay seller subscription details to check active plans, entitlements, and renewal status. Use this tool to confirm your current subscription and manage account benefits.
Get seller subscription information
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Optional subscription page size limit | |
| continuationToken | No | Optional continuation token |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / continuationTokenAdded value: +{
+ "description": "Optional continuation token",
+ "type": "string"
+}Input schema / properties / limitAdded value: +{
+ "description": "Optional subscription page size limit",
+ "type": "string"
+}Input schema / properties / limitTypeRemoved value: -{
- "description": "Optional limit type filter",
- "type": "string"
-}v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint: true, so the read-only nature is covered. The description adds no additional behavioral context such as pagination behavior, single vs. list return, or auth requirements. Since the description carries minimal behavioral disclosure beyond the annotation, it earns a low score.
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 a single, efficient sentence with no filler. It front-loads the primary action and resource. However, it might be slightly under-specified, though that is more a completeness issue than a conciseness issue.
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?
With no output schema and only a terse description, an agent cannot tell what the response looks like or what 'subscription information' includes. The optional pagination parameters hint at a list, but the description doesn't clarify. For a tool with two parameters and no output schema, this description is overly minimal.
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?
Schema coverage is 100%: both limit and continuationToken have descriptions in the input schema. The tool description adds no additional parameter semantics, but the high schema coverage sets the baseline at 3.
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 'Get seller subscription information' clearly identifies the action (get) and the resource (seller subscription information). It distinguishes from the sibling 'ebay_get_notification_subscription' by using 'seller subscription' rather than 'notification subscription', though it does not explicitly name the alternative.
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?
The description provides no guidance on when to use this tool vs. the many subscription-related siblings (e.g., ebay_get_notification_subscription). No context is given about prerequisites, scenarios, or exclusions, leaving the agent to infer usage solely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.