Create a new inventory item group or replace an existing one on eBay using the item group key and request body. Update multi-variation listing details efficiently.
Create or replace an inventory item group
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Generated InventoryItemGroup request body | |
| inventoryItemGroupKey | Yes | The inventory item group key |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.14.1Input schema / properties / bodyAdded value: +{
+ "description": "Generated InventoryItemGroup request body"
+}Input schema / properties / inventoryItemGroupRemoved value: -{
- "additionalProperties": true,
- "description": "Inventory item group details",
- "properties": {
- "aspects": {
- "additionalProperties": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "type": "object"
- },
- "description": {
- "type": "string"
- },
- "imageUrls": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "inventoryItemGroupKey": {
- "type": "string"
- },
- "subtitle": {
- "type": "string"
- },
- "title": {
- "type": "string"
- },
- "variantSKUs": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "variesBy": {
- "additionalProperties": true,
- "properties": {
- "specifications": {
- "items": {
- "additionalProperties": true,
- "properties": {
- "name": {
- "type": "string"
- },
- "values": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "required": [
- "name",
- "values"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "type": "object"
- }
- },
- "required": [
- "aspects",
- "inventoryItemGroupKey",
- "title"
- ],
- "type": "object"
-}Input schema / requiredPrevious value: -[
- "inventoryItemGroupKey",
- "inventoryItemGroup"
-]New value: +[
+ "inventoryItemGroupKey",
+ "body"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any behavioral traits beyond the action. It does not explain what 'replace' entails (e.g., full overwrite, impact on existing items) or any side effects. With no annotations, the description fails to compensate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (one short sentence). While not verbose, it lacks detail that could be added without sacrificing brevity. It is too sparse to be considered well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has two required parameters, no output schema, and no annotations, the description is insufficient. It fails to explain the body structure, replacement behavior, or any contextual details needed for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers both parameters with descriptions, so the description adds no additional meaning. Baseline of 3 is appropriate as the schema already provides basic semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Create or replace' and the resource 'inventory item group'. It is specific and matches the tool name. However, it does not differentiate this tool from siblings like ebay_create_or_replace_inventory_item or other group-related tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or exclusions. This leaves the agent without context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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