CartViral

Import products from a link

import_products

Idempotent

Import products into the account's catalog from a public link: a Shopify storefront link imports the whole published catalog (up to 750 products); a WooCommerce store link imports its catalog; a product page on Shopify, Amazon, TikTok Shop, Etsy or most other sites imports that product. Re-importing the same link updates products in place.

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": {
      "url": "<url>"
    },
    "name": "import_products"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public store or product page URL (https://...)
`html`	No	Optional: the page's HTML as the user's browser sees it (browser extension), for sites that block servers such as eBay, Etsy or Walmart

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare openWorld, non-read-only, idempotent, non-destructive; the description adds real value on top by disclosing the 750-product cap for full-catalog imports and that repeat imports update existing products in place. It leaves out what happens on partial failures or whether a 750-product import is synchronous, which keeps it below 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-loaded with the verb and resource, and every clause carries distinct information (source types, catalog cap, in-place update). It is dense with enumerated examples but none are padding; a slight trim of the site list would improve scanability.

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 two-parameter import with full schema coverage and no output schema, the description covers sources, limits, and idempotency well. The remaining gap is what the call returns or whether a large catalog import is long-running — information an agent would want before invoking it on a 750-product store.

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 goes beyond the schema's generic 'Public store or product page URL' by mapping specific link categories to specific import behaviors. The optional `html` parameter is left entirely to the schema, which is acceptable given full coverage.

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 (import products into the account's catalog) and then enumerates the distinct source types that can be imported — Shopify storefront, WooCommerce store, or a single product page — so an agent can tell exactly what this does versus list_products. The scope distinction (whole catalog vs. single product) is explicit.

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?

Clear usage context: give it a public link and the behavior depends on the link type, plus re-importing the same link updates in place rather than duplicating. It does not name an alternative tool or state when NOT to use it (e.g., private/authenticated store URLs), so it falls short of explicit alternative routing.

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

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