Skip to main content
Glama
alex-brecher

shopify-multi-store

by alex-brecher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shopify_upload_image

Destructive

Upload a local image file or HTTPS URL to Shopify Files, wait for processing, and return its CDN URL. Defaults to dry-run preview before applying.

Instructions

Upload a local image file or an HTTPS image to Shopify Files, wait for processing, and return its CDN URL (check it later with shopify_get resource uploaded_image). Defaults to dryRun:true, which previews the upload without sending anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
altNo
storeYes
dryRunNoTrue (the default) returns a before/after preview without changing anything in Shopify. Pass false, after the user authorizes this store and exact change, to apply it; the tool then reads the result back.
filenameNo
imageFileNo
sourceUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "const": true,
-  "description": "True only after authorization for this store and exact change.",
-  "type": "boolean"
-}
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": true,
+  "description": "True (the default) returns a before/after preview without changing anything in Shopify. Pass false, after the user authorizes this store and exact change, to apply it; the tool then reads the result back.",
+  "type": "boolean"
+}
    • changedInput schema / properties / sourceUrl / format
      Previous value: -"uri"New value: +"starts_with"
    • changedInput schema / required
      Previous value: -[
-  "store",
-  "confirm"
-]New value: +[
+  "store"
+]
  2. Addedv1.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructive/openWorld/non-idempotent, and the description adds real value beyond them: that the call blocks and waits for processing before returning a CDN URL, and that the default dryRun:true sends nothing to Shopify. It doesn't cover failure/timeout behavior during the wait.

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?

Two tight sentences, front-loaded with purpose then the critical dryRun default. Nothing is wasted, and the safety-relevant default is called out prominently.

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?

No output schema exists, so stating the return value (CDN URL) and the follow-up retrieval path is valuable. Combined with annotations covering the mutation profile, the definition is nearly complete, though the low parameter coverage and unspecified imageFile/sourceUrl exclusivity leave a small gap.

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?

Schema description coverage is only 17%, so the description must compensate. It clarifies the imageFile-vs-sourceUrl choice and the dryRun default, but says nothing about alt, filename, or store semantics, leaving several parameters undocumented.

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 (upload), resource (image file or HTTPS image), destination (Shopify Files), and outcome (waits for processing, returns CDN URL). It also names shopify_get's uploaded_image resource as the follow-up path, making it distinguishable from other mutation siblings.

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?

Explains the operating mode clearly: dryRun defaults to true and previews without sending anything, and points to shopify_get for later verification. It does not, however, state when to prefer imageFile over sourceUrl, or any preconditions beyond the schema's own dryRun note.

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

Deploy Server

Other Tools