Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_compatibility_property_names

Retrieve compatibility property names for eBay categories. Specify marketplace and category to list property names used in product fitment and compatibility data.

Instructions

Get compatibility property names

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesCompatibility property-name request data
marketplaceIdYesMarketplace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.14.1
    • changedInput schema / properties / data / description
      Previous value: -"Request data for getting compatibility property names"New value: +"Compatibility property-name 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 / dataset
      Added value: +{
+  "description": "Datasets to return",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • 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.9/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as read-only nature, side effects, or permissions required. The name implies a read operation, but this is not explicit.

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 concise sentence, front-loaded with the key action. However, it could benefit from slight expansion for clarity.

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 complexity of the tool with nested input parameters and no output schema, the description is too brief. It does not explain what property names are, expected output format, or how it relates to other compatibility tools.

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%, so all parameters have descriptions. The description adds no additional meaning beyond what the schema already provides, resulting in a baseline score of 3.

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 clearly states 'Get compatibility property names' which is a specific verb+resource. It indicates what the tool does, but does not differentiate from sibling tools like 'ebay_get_compatibility_property_values' or 'ebay_get_compatibilities_by_specification'.

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 guidelines are provided. The description does not specify when to use this tool vs alternatives, nor does it include preconditions or context.

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