Skip to main content
Glama

generate_product

Create marketplace-compliant e-commerce product photos with category-specific style optimization for online store catalogs.

Instructions

Generate professional e-commerce product photography that drives purchases with automatic style optimization.

Use this when:

  • Creating product photos for online stores

  • Need marketplace-compliant images (Amazon, Shopee, Tokopedia)

  • Want consistent catalog photography

  • Need category-optimized shots (food, fashion, electronics, jewelry, furniture)

NOT for:

  • Artistic or creative images (use generate_image instead)

  • Logos or branding assets (use generate_logo instead)

  • Icons or small visual assets (use generate_icon instead)

  • Editing existing product photos (use edit_image instead)

Chain with: If user requests specific pixel dimensions for marketplace requirements, chain with resize_image after generation.

Example: "generate_product productDescription='handmade leather wallet' style='premium'"

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": {
      "productDescription": "<productDescription>",
      "background": "<background>",
      "lighting": "<lighting>",
      "platform": "<platform>",
      "productCategory": "<productCategory>",
      "aspectRatio": "<aspectRatio>",
      "outputFormat": "<outputFormat>"
    },
    "name": "generate_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
contextNo
lightingYesstudio
platformYesgeneral
backgroundYeswhite
aspectRatioYes1:1
outputFormatYespng
outputFilenameNo
productCategoryYesgeneral
productDescriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.6/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden, but it only offers marketing phrases like 'drives purchases' and 'automatic style optimization.' It does not explain what the tool returns, whether images are saved or linked, how outputFilename affects results, or any latency, cost, or permission 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 definition is front-loaded and organized into purpose, when-to-use, exclusions, chaining, and an example. Most sentences earn their place, though the opening marketing language and the example are somewhat less informative than the rest.

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 tool with 10 parameters, 7 required fields, no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It covers purpose and routing well, but omits return behavior, output handling, and meaningful semantics for most parameters.

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

Parameters2/5

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

Schema description coverage is 0% across 10 parameters, and the description explains only productDescription and style through a single example. It gives useful domain context for platform and productCategory but does not clarify background, lighting, aspectRatio, outputFormat, outputFilename, context, or the enum meanings and defaults.

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: generate professional e-commerce product photography. It clearly distinguishes the tool from generate_image, generate_logo, generate_icon, and edit_image by naming those siblings and their domains.

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?

It gives explicit when-to-use bullets covering online stores, marketplace compliance, catalog consistency, and category-optimized shots. It also provides explicit NOT-for alternatives and a chaining rule with resize_image, leaving little ambiguity about tool selection.

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