ebay-mcp

ebay_get_compatibilities_by_specification

Retrieve eBay product compatibilities by specification, using filters like category, properties, and pagination to get matching vehicle or part fitment data.

Instructions

Get compatibilities by specification

Input Schema

TableJSON Schema

Name	Required	Description	Default
`marketplaceId`	Yes	Marketplace ID
`specification`	Yes	Compatibility specification object

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.14.1Jul 22, 2026

addedInput schema / properties / marketplaceId

Added value: +{
+  "description": "Marketplace ID",
+  "enum": [
+    "EBAY_AT",
+    "EBAY_AU",
+    "EBAY_BE",
+    "EBAY_CA",
+    "EBAY_CH",
+    "EBAY_CN",
+    "EBAY_CZ",
+    "EBAY_DE",
+    "EBAY_DK",
+    "EBAY_ES",
+    "EBAY_FI",
+    "EBAY_FR",
+    "EBAY_GB",
+    "EBAY_GR",
+    "EBAY_HK",
+    "EBAY_HU",
+    "EBAY_ID",
+    "EBAY_IE",
+    "EBAY_IL",
+    "EBAY_IN",
+    "EBAY_IT",
+    "EBAY_JP",
+    "EBAY_MY",
+    "EBAY_NL",
+    "EBAY_NO",
+    "EBAY_NZ",
+    "EBAY_PE",
+    "EBAY_PH",
+    "EBAY_PL",
+    "EBAY_PR",
+    "EBAY_PT",
+    "EBAY_RU",
+    "EBAY_SE",
+    "EBAY_SG",
+    "EBAY_TH",
+    "EBAY_TW",
+    "EBAY_US",
+    "EBAY_VN",
+    "EBAY_ZA",
+    "EBAY_HALF_US",
+    "EBAY_MOTORS_US"
+  ],
+  "type": "string"
+}

addedInput schema / properties / specification / properties / categoryId / description
```
Added value: +"eBay leaf category ID"
```
removedInput schema / properties / specification / properties / categoryTreeId
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / specification / properties / compatibilityProperties

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "name": {
-        "type": "string"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "name",
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / specification / properties / compatibilityPropertyFilters

Added value: +{
+  "description": "Compatibility property filters",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "propertyName": {
+        "description": "Compatibility property name",
+        "type": "string"
+      },
+      "propertyValue": {
+        "description": "Compatibility property value",
+        "type": "string"
+      },
+      "unitOfMeasurement": {
+        "description": "Property unit of measurement",
+        "type": "string"
+      },
+      "url": {
+        "description": "Property reference URL",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / specification / properties / dataset

Added value: +{
+  "description": "Dataset to return",
+  "type": "string"
+}

addedInput schema / properties / specification / properties / datasetPropertyName

Added value: +{
+  "description": "Specific dataset property names",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / specification / properties / exactMatch

Added value: +{
+  "description": "Return only exact specification matches",
+  "type": "boolean"
+}

addedInput schema / properties / specification / properties / paginationInput

Added value: +{
+  "additionalProperties": true,
+  "description": "Pagination input",
+  "properties": {
+    "limit": {
+      "description": "Maximum number of results",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Number of results to skip",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / specification / properties / sortOrders

Added value: +{
+  "description": "Compatibility property sort order",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "sortOrder": {
+        "additionalProperties": true,
+        "description": "Sort property definition",
+        "properties": {
+          "order": {
+            "description": "Sort order",
+            "type": "string"
+          },
+          "propertyName": {
+            "description": "Property name to sort by",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "sortPriority": {
+        "description": "Sort priority",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / specification / properties / specifications

Added value: +{
+  "description": "Part specifications",
+  "items": {
+    "$ref": "#/properties/specification/properties/compatibilityPropertyFilters/items"
+  },
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "specification"
-]New value: +[
+  "marketplaceId",
+  "specification"
+]

First observedv1.8.10May 31, 2026

TDQS

C2/5.0

Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It only repeats the tool name, offering no information about read-only nature, authentication needs, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, but it is under-specified rather than concise. It fails to convey necessary information within a compact structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (nested objects, no output schema, many siblings), the description is completely inadequate. It provides no context on return values, filtering, or how to use the specification field effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the input schema has 100% description coverage, the tool description adds no value in explaining the complex nested parameters or how to construct the specification object. Schema descriptions are present but the tool description does not help interpret them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it 'gets compatibilities by specification', which indicates the action and resource, but it doesn't specify what type of compatibilities (e.g., automotive parts) and fails to distinguish from sibling tools like ebay_get_product_compatibilities.

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 usage guidance is provided. The description does not indicate when to use this tool versus other compatibility-related tools such as ebay_get_compatibility_property_names or ebay_get_product_compatibilities.

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

Deploy Server

ebay_get_compatibilities_by_specification

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools