Grigora

create_commerce_collection

Destructive

Create a product collection, e.g. "New arrivals" or "Under $50". Only title is required.

Args: project_id: The project ID. title: Collection name. Required. description: Collection description. slug: URL slug. Derived from the title if empty. image_url: Cover image URL. product_ids: JSON array of product ids to link, in display order, e.g. ["abc","def"]. status: active or draft. Draft collections are not published to the storefront. sort: Manual ordering weight; lower sorts first. seo: JSON object {title, description, image_url, canonical_url, robots}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "title": "<title>"
    },
    "name": "create_commerce_collection"
  }
}

Input Schema

Name	Required	Default
`seo`	No
`slug`	No
`sort`	No
`title`	Yes
`status`	No	active
`image_url`	No
`project_id`	Yes
`description`	No
`product_ids`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, destructive=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: drafts are not published to the storefront, slug is derived from title if empty, sort weight ordering, and product_ids display order.

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?

Purpose is front-loaded in the first line, followed by a clean Args block. Given the 0% schema coverage, the per-parameter lines all earn their place rather than being redundant padding.

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

Completeness4/5

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

For a 9-parameter commerce mutation, the description covers purpose, all parameters, and several behavioral quirks. An output schema exists so return values need not be explained; only auth/permission requirements and error behavior are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the full burden—and it documents all nine parameters with meaning, including the JSON array format for product_ids (["abc","def"]) and the seo object shape ({title, description, image_url, canonical_url, robots}). This fully compensates for the empty schema.

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+resource ("Create a product collection") and clarifies the concept with two concrete examples ("New arrivals", "Under $50"). It does not explicitly differentiate from the many other create_* siblings, but the resource is distinctive enough that an agent can identify it.

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 when-to-use or when-not-to-use guidance is provided relative to alternatives like set_commerce_collection_products or add_products_to_commerce_collection. "Only title is required" is a minor helpful note, but nothing tells the agent when this tool is the right choice.

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

All Grigora tools Inspect

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

Need Help?