eBay Shipping Policy MCP
Related Servers
Alternatives to eBay Shipping Policy MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceProvides AI assistants with comprehensive access to eBay's Sell APIs, including 325 tools for inventory management, order fulfillment, marketing campaigns, analytics, and more.313385 npm162MIT
- FlicenseNot gradedqualityDmaintenanceEnables eBay sellers to manage inventory, view orders, handle messages, and browse listings through AI assistants using eBay seller APIs.-
- AlicenseAqualityDmaintenanceEnables automated LinkedIn growth by posting, commenting, and managing connections through Claude Code, with daily scheduled tasks for inbox replies and connection requests.17MIT
- AlicenseBqualityCmaintenanceEnables management of App Store Connect operations such as listing apps, managing builds, submitting for review, and handling in-app purchases through Claude Code.2510 npmMIT
- FlicenseNot gradedqualityCmaintenanceConnects Claude to your MercadoLibre seller account, enabling natural language management of listings, orders, and shipments.-
- AlicenseNot gradedqualityDmaintenanceEnables running the entire LinkedIn sales motion inside Claude Code, including content creation, audience warming, outreach, and booking calls.9MIT
TDQS
Scored across 13 tools
Tools are mostly distinct: single vs. bulk operations (delete_policy vs. bulk_delete_policies, update_exclusions vs. bulk_update_exclusions) are clear in scope, and actions like add/reorder/remove on shipping services are well separated. Minor overlap exists between bulk_update_exclusions and import_excel, but descriptions clarify the input mechanism (name filter vs. Excel).
All tool names use snake_case and follow a verb-first pattern (list, get, create, update, delete, export, import, etc.). A few names like export_all_excel and import_excel omit the explicit object, but the convention is otherwise coherent and predictable.
13 tools is a well-scoped set for an eBay fulfillment policy server. Each tool covers a concrete operation, and the count is within the ideal 3–15 range without redundancy or excess.
The domain covers policy deletion, cloning (as a create), exclusion management, and shipping services. However, there is no direct get_policy or update_policy for core policy fields (e.g., name, handling time), and no true create-from-scratch operation, which are notable gaps for a policy management workflow.