Skip to main content
Glama

Create Product

sirv_create_product

Create a product in the Studio catalogue (PIM) using a required SKU and name, for items not yet in a connected store. Returns the new product with its ID.

Instructions

Create one product in the Studio catalogue (PIM).

Use it for a product that is not in a connected store yet. Do not use it for a Shopify store's products: sirv_sync_shopify_products imports them. To add images next, use sirv_link_assets_to_product.

Inputs: sku and name are required. status defaults to active. externalId, externalSource and externalUrl record where the product comes from.

Returns the new product with its id.

Credits: free.

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": {
      "sku": "<sku>",
      "name": "<name>"
    },
    "name": "sirv_create_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesThe product's SKU, up to 100 characters
nameYesProduct name, up to 255 characters
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
statusNoProduct status. Default: activeactive
externalIdNoThe product's id in another system, such as a store
descriptionNoProduct description, up to 5000 characters
externalUrlNoThe product's page URL in that system
externalSourceNoThe system the product comes from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.1
    • changedInput schema / properties / description / description
      Previous value: -"Product description"New value: +"Product description, up to 5000 characters"
    • changedInput schema / properties / externalId / description
      Previous value: -"External system ID"New value: +"The product's id in another system, such as a store"
    • changedInput schema / properties / externalSource / description
      Previous value: -"External source"New value: +"The system the product comes from"
    • changedInput schema / properties / externalUrl / description
      Previous value: -"External product URL"New value: +"The product's page URL in that system"
    • changedInput schema / properties / name / description
      Previous value: -"Product name"New value: +"Product name, up to 255 characters"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedInput schema / properties / sku / description
      Previous value: -"Product SKU (unique identifier)"New value: +"The product's SKU, up to 100 characters"
    • changedInput schema / properties / status / description
      Previous value: -"Product status"New value: +"Product status. Default: active"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so safety profile is covered. The description adds context the annotations cannot: the return value ('Returns the new product with its id') and the cost ('Credits: free'). It does not say what happens on a duplicate SKU or invalid externalId, which matters given idempotentHint=false, so it falls short of full behavioral disclosure.

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?

Front-loaded with purpose followed by use/do-not-use routing, then 'Inputs', 'Returns' and 'Credits' in labeled chunks. Very little waste; the only redundancy is restating defaults already present in the schema ('status defaults to active').

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 an 8-parameter creation tool with no output schema, the description covers required fields, defaults, provenance semantics, the returned object and cost. The remaining gap is failure behavior — duplicate SKU handling and error conditions — which an agent would want before calling a non-idempotent create.

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 baseline is 3 and the schema already documents each field including orgId. The description adds only a small amount of extra meaning by grouping externalId/externalSource/externalUrl as provenance markers and restating the status default, but it omits any guidance on orgId or on allowed externalSource combinations.

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?

States a specific verb and resource plus scope: 'Create one product in the Studio catalogue (PIM).' It immediately distinguishes itself from sirv_sync_shopify_products and sirv_link_assets_to_product by naming what it is not for, so an agent can separate it from siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing: use it for products not yet in a connected store, do NOT use it for Shopify products (use sirv_sync_shopify_products instead), and if images are needed next, use sirv_link_assets_to_product. Both an exclusion and a follow-on alternative are named with the condition that selects them.

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