PhotoForge MCP Server

export_to_shopify

Export AI-generated fashion and product photos to Shopify product listings using an image URL and product title.

Instructions

Export AI fashion and product photos directly to Shopify product listings.

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": {
      "imageUrl": "<imageUrl>",
      "productTitle": "<productTitle>"
    },
    "name": "export_to_shopify"
  }
}

Input Schema

Name	Required	Description
`imageUrl`	Yes	Image URL to export.
`description`	No	Product description.
`productTitle`	Yes	Product title in Shopify.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies an external write operation to Shopify but does not state whether it creates a new product listing, a draft, or updates an existing one, nor does it mention authentication, permissions, or side effects.

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 a single efficient sentence with the action and destination front-loaded. There is no redundant or filler language.

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?

For a mutation tool that exports to an external platform with no annotations and no output schema, the description is too sparse. It omits whether the tool creates or updates listings, required Shopify setup, image URL accessibility constraints, and what the operation returns.

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 100%, so all three parameters are already documented in the input schema. The description adds no additional meaning about image URL requirements, title formatting, or how the optional description field is used beyond what the schema provides. Baseline 3 applies.

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 states a specific verb and resource: exporting AI fashion/product photos to Shopify product listings. It distinguishes the tool from sibling exporters like export_to_social, export_to_notion, and export_to_fanvue by naming the destination platform explicitly.

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

Usage Guidelines2/5

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

The description says what the tool does but gives no guidance on when to choose it versus the other export tools, nor does it mention prerequisites such as connecting a Shopify account. The agent is left to infer that Shopify is the destination, but not when this tool is appropriate.

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