Aalto

Move products between collections

aalto_move_products

DestructiveIdempotent

Moves products from one collection to another: adds them to the destination with the status they had in the source, then removes them from the source. Products are never deleted and always stay in the Library, so the Library cannot be the source. Shared or published collections can be neither the source nor the destination. Reports partial results instead of hiding them.

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": {
      "from_collection_id": "<from_collection_id>",
      "to_collection_id": "<to_collection_id>",
      "product_ids": "<product_ids>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "aalto_move_products"
  }
}

Input Schema

Name	Required	Description
`section_id`	No	A section of the destination to place them in.
`product_ids`	Yes	1–50 products that are currently in the source collection.
`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.
`to_collection_id`	Yes	A private collection to put them in. Must differ from the source.
`from_collection_id`	Yes	The collection to take the products out of (not the Library).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description goes well beyond them by clarifying that the 'destruction' is only removal from the source, that products survive in the Library, that source status is preserved on the destination copy, and that partial failures are surfaced rather than hidden. That is exactly the context an agent needs before invoking a destructive batch write.

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

Conciseness5/5

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

A single dense paragraph that front-loads the operation, then constraints, then result behavior. Every sentence carries distinct information; nothing is redundant with the schema or annotations.

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?

For a 5-parameter destructive batch tool with no output schema, the description covers the operation, the source/destination preconditions, the survival guarantee for products, and the partial-result reporting behavior. An agent has enough to decide and call correctly.

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 every parameter is already documented including the idempotency key, section placement, and the 1–50 product limit. The description adds only the collection-type constraints on source and destination, not field-level meaning, so the baseline 3 applies.

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 ('Moves products from one collection to another') and immediately distinguishes the semantics from sibling write tools by spelling out add-then-remove behavior. The 'never deleted, always stay in the Library' clause further separates it from create_products and update_products.

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?

Gives concrete when-not conditions: the Library cannot be the source, and shared or published collections can be neither source nor destination. It does not name sibling alternatives (e.g. when to prefer aalto_organize or update_products over a move), which keeps it short of 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?