Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_find_listing_recommendations

Read-only

Get listing recommendations from eBay's Recommendation API to optimize your Sell workflow. Specify marketplace, filters, or listing IDs to receive actionable suggestions.

Instructions

Find listing recommendations through the eBay Recommendation API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum recommendations to return
filterNoRecommendation filter expression
offsetNoRecommendations to skip before returning results
requestBodyNo
marketplaceIdYesMarketplace ID sent as X-EBAY-C-MARKETPLACE-ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.14.1
    • changedInput schema / properties / filter / description
      Previous value: -"Filter criteria"New value: +"Recommendation filter expression"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Maximum recommendations to return"
    • removedInput schema / properties / listingIds
      Removed value: -{
-  "description": "Array of listing IDs to get recommendations for",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • changedInput schema / properties / marketplaceId / description
      Previous value: -"Marketplace ID"New value: +"Marketplace ID sent as X-EBAY-C-MARKETPLACE-ID"
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip"New value: +"Recommendations to skip before returning results"
    • addedInput schema / properties / requestBody
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "listingIds": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / required
      Added value: +[
+  "marketplaceId"
+]
  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?

The readOnlyHint annotation already signals this is a safe read operation, but the description adds no behavioral context beyond that. It does not mention return format, pagination behavior, default limits, or how the optional filter/offset parameters affect results.

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 a single clear sentence with no wasted words. It is concise and readable, though it carries very little information for a tool with five parameters and nested request body structure.

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 nested requestBody, filter expression, no output schema, and a large sibling set, this description is too thin. It does not explain what recommendations are, how filtering works, whether listingIds is needed, or what a successful call returns.

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 description coverage is 80%, so the schema already documents limit, filter, offset, and marketplaceId. The description itself adds no parameter meaning, and the undocumented requestBody/listinIds parameter is not clarified, but the high schema coverage keeps this at baseline.

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 states a specific verb ('Find'), a resource ('listing recommendations'), and the API source ('eBay Recommendation API'). It clearly indicates what the tool does and distinguishes it from generic search/fetch siblings, though it does not explain what a 'listing recommendation' is.

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 about when to use this tool versus alternatives like ebay_suggest_items, ebay_find_eligible_items, or ebay_get_listing_violations. There are no usage conditions, exclusions, or references to sibling tools.

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