Skip to main content
Glama
Sign In

WhizzyCommerce

by com.whizzycommerce
OverviewDiscussionsAdmin

imports_create

Set up a product import. Money is integer minor units (cents). Calling this changes nothing: it returns a preview of what would change and a confirmation link. Only the merchant, on that page, can make it happen.

Input Schema

NameRequiredDescriptionDefault
urlYesThe file's address, the sheet's link as copied from the browser, or the Shopify store's own address (yourstore.com).
hourNoDaily or weekly: the hour, on the shop's clock.
nameYesWhat to call it, e.g. "Supplier stock, hourly".
notifyNoWhen a run's report is emailed.problems
recordNoXML only: the element one product row is, as imports.inspect lists them, e.g. rss/channel/item. Omitted, the outermost repeating element.
runNowNoRun it as soon as it is saved. The preview says what the run would add, update and leave out.
sourceYesurl for a CSV or XML file at an http(s) address; sheets for a Google Sheet shared as "anyone with the link"; shopify for a merchant moving from a Shopify store that is still online, which brings its products and their collections.
cadenceNoRun on its own this often (Pro). Omitted, it runs only when asked.
mappingNoColumn (exactly as imports.inspect lists it) to field. Only the columns to change: the rest keep the guess, or the task's saved mapping.
weekdayNoWeekly only: 1 is Monday, 7 is Sunday.
strategyNoupsert adds new products and updates existing ones; add only adds; update only updates (the rule for a stock or price file).upsert
draftMissingNoSet products to draft when they leave the file; only products this import brought in or updated, and never more than a fifth at once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"url for a CSV or XML file at an http(s) address; sheets for a Google Sheet shared as \"anyone with the link\"."New value: +"url for a CSV or XML file at an http(s) address; sheets for a Google Sheet shared as \"anyone with the link\"; shopify for a merchant moving from a Shopify store that is still online, which brings its products and their collections."
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "url",
-  "sheets"
-]New value: +[
+  "url",
+  "sheets",
+  "shopify"
+]
    • changedInput schema / properties / url / description
      Previous value: -"The file's address, or the sheet's link as copied from the browser."New value: +"The file's address, the sheet's link as copied from the browser, or the Shopify store's own address (yourstore.com)."
    • changedInput schema / properties / url / minLength
      Previous value: -8New value: +4
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds substantial context beyond annotations: calling the tool changes nothing on its own, it returns a preview plus a confirmation link, and only the merchant on that page can complete it — critical for an agent that might otherwise retry expecting effects. It also flags money as integer minor units. Remaining gap: nothing addresses repeat calls or the non-idempotent nature declared in annotations.

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?

Four short sentences, front-loaded with the action, then the money-format caution, then the crucial safety note. No filler, no restatement of the title, and each sentence earns its place.

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 12-parameter creation tool with a nested mapping object, high schema coverage and annotations already covering safety, this is close to complete: the flow, the preview behavior, and the money unit are all covered. What remains missing given the absence of an output schema is any hint of what the preview response looks like.

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 100%, so the schema carries the parameter documentation and baseline would be 3. The description adds one genuinely non-obvious semantic not in the schema — money values are in minor units (cents) — which prevents a real class of misuse. It stops there, though; nothing further on the nested mapping or cadence parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: "Set up a product import." An agent immediately knows the operation. However, it does not distinguish itself from the close siblings imports_update, imports_run, and imports_inspect, leaving ambiguity about which of these sets a new import up versus modifies an existing one.

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

Usage Guidelines3/5

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

The description conveys the two-phase flow (preview then merchant-confirmed execution), which implies when this tool is appropriate. But it never names an alternative or an exclusion — nothing says when to use imports_update instead of imports_create, or that imports_run is the tool to trigger a run later. Usage is implied rather than stated.

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

All WhizzyCommerce toolsInspect
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