Skip to main content
Glama

Import a product from its page URL

import_product_from_url

Import a product from its storefront URL to begin creating short-form videos. Returns a product ID instantly, runs scraping and video drafting in the background, and avoids duplicate imports.

Instructions

Start a new InstantClips product from a product page URL (a storefront listing, e.g. a Shopify product page).

Returns immediately with a product_id — the scrape, the image download and the first video-direction draft all run in the background. Poll get_product until import_status is "imported" and video_direction.drafting is false, which usually takes under a minute.

Pasting a URL that was already imported on this account returns that existing product instead of creating a duplicate.

If the storefront name does not exactly match a brand this account has already reviewed, the import stops on a brand decision instead of guessing: get_product will report brand_decision_required, and no video direction is drafted until it is resolved with create_brand or set_product_brand. Do not assume the account's existing brand — a product from a different company drafted under the wrong brand's voice is the failure this prevents. Pass brand_id only when the user has told you which brand this product belongs to.

This does not spend credits. Only generate_video does.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe product page URL, e.g. https://store.example.com/products/wool-runner
brand_idNoOptional, and only when the user has said which brand this is. Omit it to let the import match the storefront against the account's brands and ask when it cannot. Use `list_brands` to see what exists.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes far beyond the annotations by disclosing the asynchronous behavior, the immediate product_id return, the background scrape/download/draft, the polling condition, duplicate-URL handling, the brand-decision stop state, and the credit policy. This is exactly the behavioral context an agent needs.

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?

The description is front-loaded with the core action and return behavior, then adds only high-value operational details. Every paragraph earns its place, and the asynchronous and brand-decision caveats are clearly separated without redundancy.

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?

Despite having no output schema, the description fully covers what the agent needs: the immediate return, how to check completion, duplicate handling, the brand-decision failure mode, the resolution path, and the credit implications. This is complete for a complex side-effecting tool.

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 adds meaningful value for brand_id by explaining when it is appropriate to pass it, how the tool behaves without it, and that list_brands exists for discovery. The url parameter is adequately covered by the schema.

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: 'Start a new InstantClips product from a product page URL.' It clearly differentiates this import-from-URL tool from sibling creation paths, especially create_product_from_images, by the input source and the background-import behavior.

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?

Gives explicit when-to-use guidance, including when to pass brand_id ('only when the user has told you which brand'), when not to assume a brand, and how to resolve a brand decision using create_brand or set_product_brand. Also tells the agent to poll get_product and clarifies that generate_video is the only credit-spending tool.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/InstantStudioAI/instantclips-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server