Aalto

Create products

aalto_create_products

Idempotent

Creates up to 25 products from details you already have (name, brand, price, specs, tags, section). Every item needs a name or a source_url; URL-only items fill in their details automatically, using one AI product import each; once this month's are used up they are skipped (reason ai_import_limit_reached), and items with a name use none. Skips items whose source_url or exact sku is already in the workspace, reporting the existing id. Stops at the plan's product limit (Free: 100 products) and reports what was created. Products always land in the Library, plus collection_id if given.

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": {
      "products": "<products>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "aalto_create_products"
  }
}

Input Schema

Name	Required	Description
`products`	Yes	1–25 products. Each needs a name or a source_url.
`collection_id`	No	A private collection to add them to. They always land in the Library too.
`idempotency_key`	Yes	Required. A new unique string per intended change (8–128 chars). Retrying with the same key and same arguments replays the first result instead of writing twice.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations with the real behavioral traits: AI-import quota is consumed per URL-only item and exhausted ones are skipped with reason ai_import_limit_reached, duplicates matched on source_url or exact sku are skipped and the existing id returned, creation halts at the plan product limit, and everything lands in the Library. These are exactly the surprises an agent needs to anticipate.

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 the action and the cap, then successive sentences each carry a distinct constraint (import quota, dedupe, plan limit, library placement). Dense but nearly every clause earns its place; the nested parenthetical exception clauses make it slightly harder to scan.

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

Completeness5/5

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

With no output schema, the description still explains what comes back (existing ids for skipped items, a report of what was created) and covers the partial-success semantics of a batch write. Nothing material for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by stating the per-item name-or-source_url rule and clarifying that section requires collection_id and that the collection is additive to the Library. It stops short of explaining fields it doesn't mention (currency, sale_price, kind).

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?

Opens with a specific verb and resource plus a hard bound: 'Creates up to 25 products from details you already have'. It implicitly separates itself from the URL-import and preview siblings by describing the batch-create path and when per-item AI import kicks in.

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

Usage Guidelines4/5

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

It gives concrete selection criteria: use this when you already have item details, URL-only items will be auto-filled, and items with a name consume no AI imports. It doesn't name a sibling like aalto_save_product_from_url or aalto_import_start explicitly, so an agent must infer the alternative, which keeps it just below a 5.

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

All Aalto 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?