Skip to main content
Glama

Check a product import

preview_catalog_import
Read-onlyIdempotent

Checks rows from your spreadsheet before importing them as your own products (sold to Printlooper sellers): which rows have problems, how many products and variants it makes, and whether your plan has room. Changes nothing. 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>"
    },
    "name": "preview_catalog_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces that with "Changes nothing." Beyond annotations it discloses genuinely useful behavior: validation rules for each row, the same-title-becomes-variants grouping rule, and that the check includes plan capacity. It does not say whether row-level errors are returned by index or position, which limits how actionable the preview feedback is described as being.

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 and the read-only guarantee are front-loaded, and nearly every clause carries information an agent needs. The single dense paragraph mixes in promotional parentheticals ("sold to Printlooper sellers", "printed on the card in the box") that add length without helping the call, and a structured field list would read better than the run-on sentence.

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?

With no output schema, the description does the right job of describing returns — problem rows, product/variant counts, plan headroom — and the rich row contract is documented at the field level. The remaining gaps are edge-behavior details (how per-row failures are keyed, behavior on the 500-row cap) that are minor for a preview endpoint but not fully covered.

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% and the single `rows` parameter is an array of 13 nested properties, so the description must carry the load — and it largely does, covering required fields (title, wholesale_price, photo_url), variant grouping semantics, and every optional field except storefront_price and tags. It omits structural constraints that live only in the schema (max 500 rows, field max-lengths, tags accepting a string or array), so it is not fully self-sufficient.

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?

The description opens with a specific verb and resource ("Checks rows from your spreadsheet before importing them as your own products") and immediately states the three things it reports: problem rows, resulting product/variant counts, and plan capacity. "Changes nothing" cleanly separates it from an actual import, so an agent can distinguish it from import_catalog without inspecting either schema.

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?

Timing guidance is explicit — use it to check rows before importing them — and a prerequisite is stated ("Needs a connected Printlooper account"). It does not name import_catalog as the follow-up alternative, so routing is implied rather than spelled out, which keeps this below a 5.

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