Skip to main content
Glama

ebay_create_or_replace_inventory_item_group

Create or replace an eBay inventory item group to manage product variations, including title, description, images, and variant SKUs.

Instructions

Create or replace an inventory item group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inventoryItemGroupKeyYesThe inventory item group key
inventoryItemGroupYesInventory item group details
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'create or replace' implying mutation, but fails to disclose idempotency, side effects (e.g., whether existing related inventory items are affected), or required permissions. For a mutating tool, this is insufficient.

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

Conciseness3/5

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

The description is a single short sentence, making it concise, but it lacks structure or additional context. While front-loaded, it could benefit from more detail without becoming verbose.

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 creating/replacing inventory item groups with nested objects, the description is too sparse. It does not explain the relationship between inventory item groups and individual inventory items, or provide any context about when to create vs replace, leaving the agent with inadequate information.

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 parameters. The description adds no additional meaning beyond the schema, earning 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 states 'Create or replace an inventory item group,' which clearly identifies the action and resource. It distinguishes from sibling tools like ebay_delete_inventory_item_group and ebay_get_inventory_item_group. However, it does not clarify the semantics of 'replace' (e.g., whether it is idempotent or performs a full replacement).

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?

The description provides no guidance on when to use this tool versus alternatives such as ebay_delete_inventory_item_group or ebay_get_inventory_item_group. It does not mention prerequisites, scenarios for create vs replace, or any context about inventory item groups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YosefHayim/ebay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server