Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_move_store_category

Move a custom eBay Store category under a new parent, then poll the returned task ID until eBay completes the change.

Instructions

Move one custom eBay Store category under a new parent (Stores API moveStoreCategory). Pass categoryId, destinationParentCategoryId (-999 for top level), and listingDestinationCategoryId when a leaf category with listings stops being a leaf. Asynchronous: eBay accepts the change and returns { taskId, location } from the Location header; poll ebay_get_store_task with taskId (or ebay_get_store_tasks) until the task is COMPLETED or FAILED. Only one store category change (add, rename, move, or delete) can be in flight at a time; eBay rejects a new change until the previous task finishes. Requires an active eBay Store subscription (sell.stores scope).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryIdYeseBay Store custom category ID from ebay_get_store_categories (not an eBay marketplace category ID)
destinationParentCategoryIdYesNew parent store category ID; pass -999 to move the category to the top level
listingDestinationCategoryIdNoNeeded only when the moved leaf category has listings and stops being a leaf; its listings move to this store category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.0

TDQS

A4.4/5.0
Behavior5/5

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

With only readOnlyHint=false supplied by annotations, the description carries the full behavioral burden and does so well: it discloses asynchronous acceptance, the returned taskId/location, polling requirements until COMPLETED or FAILED, a concurrency limit, and the required sell.stores scope.

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 front-loaded with purpose and then adds operational details in a logical order. It is somewhat dense and includes some schema-repeating parameter instructions, but nearly every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema mutation tool, this is highly complete: it explains async return handling, polling follow-up, concurrency limits, prerequisites, and the exact conditions for optional parameters.

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 100%, so the schema already documents all three parameters in detail. The description repeats the parameter usage (including -999 and the leaf-listing condition) but adds no meaningful semantics 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 states a precise verb and resource ('Move one custom eBay Store category under a new parent'), names the underlying API operation, and distinguishes the target from marketplace categories. It also clearly separates this move operation from add/rename/delete store category changes.

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

Usage Guidelines4/5

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

It gives strong context: async behavior, polling via named sibling tools, the one-change-at-a-time constraint, and the required eBay Store subscription. It does not explicitly route to add/rename/delete alternatives, but the usage conditions and exclusions are otherwise clear.

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