Skip to main content
Glama

Marketplace and ad images for a market

image_studio
Read-onlyIdempotent

Plan the product image set for one market: the marketplace's main-image rules (Amazon, Rakuten, Tmall, Shopee, TikTok Shop…), a 7-image gallery (real main image, local lifestyle, texture, how-to, benefits infographic, scale, trust) with edit-from-packshot prompts for treg.to image models, ad sizes per platform, AI and claims rules, and the estimated cost. Like video_studio it puts the market's sale gates (sale_gate), the rules that bind ads and listings (ad_rules) and wording to change (claims_check) first, and signed in it builds the trust image from the certifications the company actually holds there. Free, read-only.

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": {
      "country": "<country>"
    },
    "name": "image_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
copyNoOptional: your own ad copy, captions, voice-over script or listing text for this market; claims_check flags wording that does not fit the market's rules and says what to use instead.
itemNoProduct as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2005' kimchi, '3305' shampoo) with live UN Comtrade imports. Optional; sets the product group.
traitsNoOptional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), contact_lens (HS 9001: contact lenses, colour lenses), hair_dye, hair_loss, acne, antiperspirant, dandruff, fluoride (toothpaste), human_derived (human stem cell culture media, human placenta, cord blood: a ban in the EU, UK, China and ASEAN), stem_cell (stem cell culture media whose source is not named: check it), exosome, radio (Bluetooth, Wi-Fi, cellular), battery, meat, dairy, egg, aerosol, flammable, industrial or household (for HS codes that hold both, such as 8414 fans, compressors and vacuum pumps: picks machinery rules, trade fairs and buyer searches, or household-appliance ones). Also detected from item, product and description; the answer lists them in product_traits.
countryYesTarget country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name.
productNoThe product in plain English as it looks.
variantsNoGenerated variants per frame.
descriptionNoOptional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the rules within one HS code (see traits) and the concepts, price tier, certifications and markets already selling that change which market fits (product_profile, entry_paths).
marketplaceNoOptional marketplace, e.g. 'amazon', 'rakuten', 'shopee'; defaults to the market's main one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / description / description
      Previous value: -"Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', 'Bluetooth speaker with a rechargeable battery', 'ramen with beef broth'). Used only to detect product traits that change the rules within one HS code (see traits)."New value: +"Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the rules within one HS code (see traits) and the concepts, price tier, certifications and markets already selling that change which market fits (product_profile, entry_paths)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / copy
      Added value: +{
      +  "description": "Optional: your own ad copy, captions, voice-over script or listing text for this market; claims_check flags wording that does not fit the market's rules and says what to use instead.",
      +  "type": "string"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', 'Bluetooth speaker with a rechargeable battery', 'ramen with beef broth'). Used only to detect product traits that change the rules within one HS code (see traits).",
      +  "type": "string"
      +}
    • addedInput schema / properties / traits
      Added value: +{
      +  "description": "Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), contact_lens (HS 9001: contact lenses, colour lenses), hair_dye, hair_loss, acne, antiperspirant, dandruff, fluoride (toothpaste), human_derived (human stem cell culture media, human placenta, cord blood: a ban in the EU, UK, China and ASEAN), stem_cell (stem cell culture media whose source is not named: check it), exosome, radio (Bluetooth, Wi-Fi, cellular), battery, meat, dairy, egg, aerosol, flammable, industrial or household (for HS codes that hold both, such as 8414 fans, compressors and vacuum pumps: picks machinery rules, trade fairs and buyer searches, or household-appliance ones). Also detected from item, product and description; the answer lists them in product_traits.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, and the description is consistent with them ('Free, read-only'). It adds genuine behavioral context beyond the annotations, notably that signed-in state changes the trust image (built from certifications the company actually holds) and that a cost estimate is produced. What it does not disclose is anything about latency, output format, or what happens when optional market/product inputs are omitted, so this is solid but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is one sprawling run-on sentence with heavy parenthetical enumerations and internal jargon (treg.to, sale_gate, ad_rules, claims_check) that a first-time caller must decode. Much of that detail belongs in the sibling tools' definitions; the image_studio-specific core could be stated in half the words.

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?

For an 8-parameter planning tool with no output schema, the description does the necessary work of telling the agent what comes back: a rules-first section, a gallery with prompts, ad sizes and a cost estimate. Only the handling of optional inputs (e.g. what defaults when marketplace/product/description are omitted) is left unaddressed.

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 every parameter is already documented in the schema, and the description does not add syntax or format detail beyond that. It does echo some downstream meaning (traits surfaced as product_traits, claims_check flagging copy) but largely restates what the schema carries, so the baseline 3 is appropriate.

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?

Opens with a specific verb+resource+scope ('Plan the product image set for one market') and then enumerates the concrete deliverables: main-image rules per marketplace, a 7-image gallery, edit-from-packshot prompts, ad sizes, AI/claims rules and estimated cost. It explicitly distinguishes itself from the sibling video_studio, so an agent can tell the two media-planning tools apart without opening either schema.

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?

The framing 'for one market' plus the parallel to video_studio makes the use case clear (image planning vs. video planning), and 'sale_gate/ad_rules/claims_check first' tells the agent what the output prioritizes. However, there is no explicit when-not-to-use statement or named alternative for overlapping tasks like channel_plan or gtm_plan, so routing is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.