Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_bulk_create_or_replace_sales_tax

Bulk create or replace sales tax tables for eBay jurisdictions. Provide country codes, jurisdiction IDs, and tax percentages to update tax settings in a single request.

Instructions

Bulk create or replace sales tax tables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestsYesArray of sales tax requests

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.1
    • changedInput schema / properties / requests / items / additionalProperties
      Previous value: -trueNew value: +false
    • changedInput schema / properties / requests / items / properties / salesTaxBase / additionalProperties
      Previous value: -trueNew value: +false
  2. Changed5 schema fields changedv1.12.0
    • removedInput schema / properties / requests / additionalProperties
      Removed value: -true
    • addedInput schema / properties / requests / items
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "countryCode": {
+      "type": "string"
+    },
+    "jurisdictionId": {
+      "type": "string"
+    },
+    "salesTaxBase": {
+      "additionalProperties": true,
+      "properties": {
+        "salesTaxPercentage": {
+          "type": "string"
+        },
+        "shippingAndHandlingTaxed": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "salesTaxPercentage"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "countryCode",
+    "jurisdictionId",
+    "salesTaxBase"
+  ],
+  "type": "object"
+}
    • removedInput schema / properties / requests / properties
      Removed value: -{
-  "requests": {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "countryCode": {
-          "type": "string"
-        },
-        "jurisdictionId": {
-          "type": "string"
-        },
-        "salesTaxBase": {
-          "additionalProperties": true,
-          "properties": {
-            "salesTaxPercentage": {
-              "type": "string"
-            },
-            "shippingAndHandlingTaxed": {
-              "type": "boolean"
-            }
-          },
-          "required": [
-            "salesTaxPercentage"
-          ],
-          "type": "object"
-        }
-      },
-      "required": [
-        "countryCode",
-        "jurisdictionId",
-        "salesTaxBase"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedInput schema / properties / requests / required
      Removed value: -[
-  "requests"
-]
    • changedInput schema / properties / requests / type
      Previous value: -"object"New value: +"array"
  3. First observedv1.8.10

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, and the description only states the action without disclosing behavioral traits like whether existing entries are replaced or errors on conflicts, rate limits, or prerequisites.

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

Conciseness5/5

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

The description is a single sentence with no redundant information, efficiently conveying the core action.

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?

For a bulk mutation tool, more context is needed (e.g., behavior on existing entries, response format) beyond what is provided. The lack of output schema and brief description leaves gaps.

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% with the 'requests' parameter described as 'Array of sales tax requests', but the description adds no further meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the action (bulk create or replace) and the resource (sales tax tables), distinguishing it from the singular sibling 'ebay_create_or_replace_sales_tax'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this vs. alternatives like the singular create/replace. Usage is implied by the 'bulk' prefix but not elaborated.

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