Skip to main content
Glama

Import products

import_catalog
Destructive

Imports rows from your spreadsheet as your own products, published to Printlooper sellers. Run preview_catalog_import first and get the user to agree. All rows must be valid; nothing is imported if any row has a problem. Rows from the shop spreadsheet, one per product or variant. Each needs title, wholesale_price (your price to sellers) and photo_url (a public https image). Rows with the same title become variants of one product (give variant_title and optional variant_sku and variant_price). Optional: description, tags, storefront_price, material_label, care_instructions and warnings (at least 40 characters each, printed on the card in the box). Needs a connected Printlooper account.

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": {
      "rows": "<rows>",
      "confirm": "<confirm>"
    },
    "name": "import_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds meaningful behavior: atomic all-or-nothing validation, publication side effect to sellers, the requirement of a connected Printlooper account, and row-collapsing rules for variants. It stops short of disclosing reversibility/undo or what an errored row response looks like, so not a 5.

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-loads the action, then prerequisites, then per-field rules, so scanning order matches decision order. It is dense with no filler, though the fragment 'Rows from the shop spreadsheet, one per product or variant' reads awkwardly and the field list runs long.

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 destructive, zero-schema-coverage bulk write with no output schema, the description supplies prerequisites, atomicity, account requirements and most field meanings. The remaining gap is outcome information — what is returned on success or failure — which matters for an agent recovering from a rejected batch.

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 description coverage is 0%, so the description carries the burden and largely does: it explains wholesale_price as 'your price to sellers', photo_url as a public https image, the same-title-becomes-variant grouping, and the 40-character minimum on warnings. It leaves 'confirm', 'tags', and the 500-row cap unmentioned, so the coverage is strong but incomplete.

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 — imports spreadsheet rows as the user's own products published to Printlooper sellers — and implicitly separates itself from preview_catalog_import by requiring that preview first. An agent can tell exactly what this does and what it produces.

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 prerequisite sequencing: 'Run preview_catalog_import first and get the user to agree,' plus the hard condition that all rows must be valid or nothing imports. That names the alternative tool and the human-confirmation gate an agent must respect before calling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources