Skip to main content
Glama

GoodBarber

by dev.goodbarber
OverviewDiscussionsAdmin

Create product

shop_create_product

Creates a product for the shop. Guidance: Creates a product for the shop. | context: title

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoProduct slug (used in its access URL).
tagsNoSet of tags associated with the product.
brandNoProduct brand platform.
mediaNoUnique ID of the slide selected as the product thumbnail.
titleYesProduct name.
statusNoProduct publishing status.- **DRAFT**: the product is being prepared and is not visible to the customers yet - **PUBLISHED**: the product is ready and available in the shop - **INVISIBLE**: the product is not visible to the customers
summaryNoProduct short description.
highlightNoBoolean indicating if the product should be showcased in the shop products list or not.
meta_titleNoProduct SEO title (for referencing by search engines).
collectionsNoList of the collections (unique IDs) to which the product belongs.
product_refNoProduct reference ID.
visibility_endNoRFC 3339 datetime with timezone until which the product should remain visible, for example 2026-07-31T18:00:00+02:00. Omit to keep the product visible until it is manually hidden or removed.
meta_descriptionNoProduct SEO description (for referencing by search engines).
visibility_startNoRFC 3339 datetime with timezone from which the product should become visible, for example 2026-07-15T09:30:00+02:00. Omit to make the product visible as soon as it is published.
show_similar_productsNoBoolean indicating whether the "Similar products" section should be displayed in the shop for this product or not.
set_custom_similar_productsNoManually defined list of similar products (unique product IDs are expected). The product field `custom_similar_products` will be filled with these products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The description explicitly says 'creates', which is consistent with the readOnlyHint false annotation. However, it does not disclose further behavior (e.g., whether the product becomes visible immediately or what happens on validation failure). Given annotations already cover readOnly and destructive hints, this is adequate but not detailed.

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

Conciseness2/5

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

While the core sentence is concise, the presence of the redundant and confusing extra text 'Guidance: Creates a product for the shop. | context: title' detracts from the structure. This unnecessary repetition would confuse an agent reading the description.

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?

For a complex operation with 16 parameters and no output schema, the description provides minimal context. It does not mention what the function returns, what side effects occur beyond creation, or any constraints like required fields (though those are in the schema). This leaves the agent with incomplete information about the tool's overall behavior.

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?

The schema description coverage is 100%, with each parameter already well-documented. The description adds no additional semantic information about the parameters, so the baseline score of 3 is appropriate.

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 'Creates a product for the shop' clearly states the verb (creates), resource (product), and scope (shop), distinguishing it from sibling tools like shop_create_option or shop_create_variant.

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?

No explicit guidance is given on when to use this tool versus alternatives such as shop_create_option or shop_create_variant. The context signals and sibling list imply usage, but the description itself lacks any such direction.

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

All GoodBarber toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources