Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_create_shipping_fulfillment

Create shipping fulfillment for an eBay order, providing line items and tracking details to complete the shipment.

Instructions

Create a shipping fulfillment for an order.

Required OAuth Scope: sell.fulfillment Minimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
orderIdYesThe unique identifier of the order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • addedInput schema / properties / body
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "lineItems": {
+      "description": "Line items to fulfill",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "lineItemId": {
+            "type": "string"
+          },
+          "quantity": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "lineItemId"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shippedDate": {
+      "description": "Date the items were shipped (ISO 8601 format)",
+      "type": "string"
+    },
+    "shippingCarrierCode": {
+      "description": "Shipping carrier code",
+      "type": "string"
+    },
+    "trackingNumber": {
+      "description": "Tracking number for the shipment",
+      "type": "string"
+    }
+  },
+  "required": [
+    "lineItems"
+  ],
+  "type": "object"
+}
    • removedInput schema / properties / fulfillment
      Removed value: -{
-  "additionalProperties": true,
-  "description": "Shipping fulfillment details including tracking number",
-  "properties": {
-    "lineItems": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "lineItemId": {
-            "type": "string"
-          },
-          "quantity": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "lineItemId"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "shippedDate": {
-      "type": "string"
-    },
-    "shippingCarrierCode": {
-      "type": "string"
-    },
-    "trackingNumber": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "lineItems"
-  ],
-  "type": "object"
-}
    • changedInput schema / properties / orderId / description
      Previous value: -"The order ID"New value: +"The unique identifier of the order"
    • changedInput schema / required
      Previous value: -[
-  "orderId",
-  "fulfillment"
-]New value: +[
+  "orderId",
+  "body"
+]
  2. First observedv1.8.10

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It states the action (create) implying mutation, but does not disclose side effects, required order state, rate limits, or idempotency. Minimal behavioral disclosure beyond the action itself.

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 very short (one sentence plus OAuth scope) and front-loaded. It is concise, but could be more structured with bullet points for readability. No wasted words.

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, no usage guidelines, no behavioral details. For a write operation with nested objects and required parameters, the description is insufficient to fully guide an AI agent. Missing prerequisites like order existence or payment status.

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 50% (only orderId has a description; body lacks one). The description adds no parameter meaning beyond the schema. Baseline is 3 due to partial coverage, and no extra value is added.

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 'Create a shipping fulfillment for an order,' using a specific verb (create) and resource (shipping fulfillment) with context. It distinguishes from sibling tools like ebay_get_shipping_fulfillments (read) and ebay_issue_refund (different action).

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 on when to use this tool versus alternatives (e.g., when an order is ready, prerequisites like payment status). Only OAuth scope is mentioned, but no exclusions or context hints.

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