Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_compatibility_property_values

Retrieve valid compatibility property values for eBay listings by specifying category, property name, and filters. Get precise fitment values to ensure correct product compatibility.

Instructions

Get compatibility property values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesCompatibility property-value request data
marketplaceIdYesMarketplace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.14.1
    • changedInput schema / properties / data / description
      Previous value: -"Request data for getting compatibility property values"New value: +"Compatibility property-value request data"
    • addedInput schema / properties / data / properties / categoryId
      Added value: +{
+  "description": "eBay leaf category ID",
+  "type": "string"
+}
    • removedInput schema / properties / data / properties / categoryTreeId
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / data / properties / propertyFilters
      Added value: +{
+  "description": "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 / data / properties / propertyName
      Added value: +{
+  "description": "Property name whose values should be returned",
+  "type": "string"
+}
    • addedInput schema / properties / data / properties / sortOrder
      Added value: +{
+  "description": "Property value sort order",
+  "type": "string"
+}
    • removedInput schema / properties / data / properties / specification
      Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "categoryId": {
-      "type": "string"
-    },
-    "categoryTreeId": {
-      "type": "string"
-    },
-    "compatibilityProperties": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "name": {
-            "type": "string"
-          },
-          "value": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "value"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}
    • 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"
+}
    • changedInput schema / required
      Previous value: -[
-  "data"
-]New value: +[
+  "marketplaceId",
+  "data"
+]
  2. First observedv1.8.10

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, and the description does not disclose any behavioral traits such as read-only nature, required permissions, or side effects. The agent cannot infer behavior beyond the name.

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 is under-specified. It is not front-loaded with key details; it omits important scoping information.

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?

No output schema is provided, and the description does not explain what the tool returns. Given the complexity of the input and many sibling tools, the description is incomplete.

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?

Input schema coverage is 100%, so parameters are described in the schema. However, the description adds no additional meaning or usage hints for complex structures like propertyFilters.

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 'Get compatibility property values' specifies a verb and resource, but it is vague and does not differentiate from siblings like ebay_get_compatibility_property_names or ebay_get_multi_compatibility_property_values. It lacks clarity on what exactly 'compatibility property values' means.

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 on when to use this tool versus alternatives. With many compatibility-related sibling tools, the agent has no basis to choose this one.

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