Skip to main content
Glama

collections_edit

Change a category. Money is integer minor units (cents). Calling this changes nothing: it returns a preview of what would change and a confirmation link. Only the merchant, on that page, can make it happen.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoThe category's name as shown in menus and at the top of its page, e.g. "Kitchen".
handleNoA new web address segment. Changing it breaks every link and search result pointing at the old one, so only when asked for.
parentNoWhere it sits: a category by id, handle or exact title, or null to move it to the top level. Omit to leave it where it is.
imageUrlNoAbsolute URL of the category's picture, used by menus and category tiles. Empty clears it.
positionNoIts place among its siblings, 0 for first, counted among the siblings it will have after this change. Omit to keep its place.
seoTitleNoThe title search results show for this category page, about 60 characters. Empty falls back to its name.
isVisibleNofalse hides the category from menus and listings; it still opens at its address, which is how a soft launch works.
collectionYesThe category to change, by id, handle or exact title.
descriptionNoPlain text shown at the top of the category page. Empty clears it.
seoDescriptionNoThe line under the title in search results, about 155 characters. Empty falls back to its description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior1/5

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

The description asserts "Calling this changes nothing," which is the definition of a read-only operation, yet the annotations declare readOnlyHint=false. This is a direct conflict about whether the environment is modified, so the agent gets contradictory signals about the tool's mutability. Annotation contradiction.

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 core sentences about the preview/confirmation flow are front-loaded and efficient. However, the standalone "Money is integer minor units (cents)" sentence is a non-sequitur for this tool and does not earn its place.

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

Completeness3/5

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

For a 10-parameter mutation-flow tool the schema carries the parameter detail, and the description usefully explains the two-phase preview/confirm behavior. But the unresolved mutability conflict with readOnlyHint=false, plus the absence of any when-to-use guidance, leaves the agent with an incomplete and inconsistent picture.

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 ten parameters in detail and the description need not compensate. The one parameter-ish note it does add, "Money is integer minor units (cents)," is irrelevant here because no money parameter exists, so it adds no real semantic value.

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?

States a specific verb and resource ("Change a category") that clearly separates it from siblings like collections_create, collections_delete, and collections_add_products. Minor terminology drift between the tool name (collections_edit) and the word "category" used throughout, but the intent is unambiguous.

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

Usage Guidelines3/5

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

The description explains what happens when you call it but never says when to reach for it versus alternatives, and there are no exclusions or prerequisites. Usage is only implied (use it to modify an existing category's attributes).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources