Skip to main content
Glama

shopify_create_file

DestructiveIdempotent

Create Shopify files from public or staged URLs to use real imagery in theme templates and pages. Upload up to 50 files per call for images, videos, 3D models, and more.

Instructions

Create shop files (images/media) from public URLs or staged resource urls, so real imagery can be referenced from theme templates and pages. Pass a single file inline, or a files list for up to 50 per call.

Args:
    original_source: Public URL or staged resource_url for a single file. Required unless files is given.
    content_type: Shopify file content type: IMAGE (default), FILE, VIDEO, EXTERNAL_VIDEO, MODEL_3D.
    alt: Alt text for the single-file form.
    filename: Filename override for the single-file form.
    files: JSON-string list of files (max 50): [{original_source, content_type?, alt?, filename?}]. Replaces the single-file fields when provided.
    project_id: Authenticated Project UUID.
    project_ref: Exact project correlation reference.
    connector_account_ref: Project-bound connector account alias.
    idempotency_key: Stable business-action identity.
    effect: Claimed read or write effect; Spring verifies it.
    approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
altNo
filesNo
effectNo
filenameNo
project_idNo
project_refNo
approval_refNo
content_typeNoIMAGE
idempotency_keyNo
original_sourceNo
connector_account_refNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Addedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

The description does not disclose side effects, idempotency guarantees, or destructive implications beyond the annotation hints. It fails to explain the destructive nature suggested by destructiveHint=true or clarify idempotency behavior.

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?

The description is concise and well-structured with an initial summary followed by parameter details. Slight redundancy in the first sentence but overall efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description omits the output schema, fails to explain when generic context parameters are required, and does not mention return values or error behavior. This leaves significant gaps for a tool with 11 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning for the primary functional parameters (original_source, content_type, alt, filename, files) but leaves the generic context parameters (project_id, project_ref, connector_account_ref, idempotency_key, effect, approval_ref) unexplained. With schema coverage at 0%, this partial coverage is insufficient to fully compensate.

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 clearly states the tool's purpose: creating shop files from public URLs or staged resources, with a specific verb ('Create') and resource ('shop files'). It distinguishes itself from sibling tools like attach_product_media or stage_upload by focusing on file creation.

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?

It provides usage guidance for single vs. batch mode ('Pass a single file inline, or a files list for up to 50 per call') but lacks explicit when-to-use vs. alternatives. No mention of choosing this over other file-related tools.

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

Install Server

Other Tools

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/RPasquale/lightbulb-mcp'

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