Skip to main content
Glama

Export GTM plan for a product

gtm_plan
Read-onlyIdempotent

START HERE. One call returns the export go-to-market plan for a product: which countries to sell to (UN Comtrade imports × reply rates from 2.2M real export emails, compared within the product's industry, plus the next-best markets to compare), which buyer types reply there, how many follow-ups to send, the channels (creator seeding and marketplaces for consumer goods; buyer lists and trade shows for industrial goods; see motion), compliance flags with an official source link (compliance_gate marks approvals that block the market until they pass; channel_plan.packaging adds EU packaging EPR), a before_you_sell checklist (sanctions, FTA and proof of origin, trademark, payment terms, holidays, re-export hubs), the official tariff lookup (tariff_by_market compares the markets side by side), data_first (where the data would start even when you pass a country), gated_markets (compared markets with such a gate), banned_markets (those of them closed outright by an ingredient ban, such as ingredients of human origin: no approval opens them, so data_first, the market the data picks and next_markets skip them), next_markets (where to move at week 13, by the same rule as data_first, skipping gated markets and exclude), English email drafts (first email, follow-ups, week-3 sample check-in, and quote_reply_email for when a buyer asks for a price first; for Japan the same drafts in Japanese as local_emails, first_email_variants included; offers TradeGraph cannot know you make are marked [CONFIRM: ...] unless you pass strengths, and first_email.localize gives the register, greeting and closing for translating to the market's language), reply_target (expected replies from the product's own industry in that market, sends for 10 replies, the week-13 rule; reply_pace checks your numbers against it each week), a 13-week schedule, buyer_sources (trade fairs with the next edition's dates, city and book_meetings_from, 6 weeks before; BuyKOREA, KOTRA), and the exact treg.to endpoints (ids + prices) to execute it. blind_spots lists what exporters miss in the focus market beyond the category's compliance pointer, triggered by the exact HS code and product traits (product_traits; pass description or traits): rules that can stop the sale, approvals before import, extra duties or charges and filings, each with who acts, the date it applies from, the official source and the date checked; blind_spots_by_market names them for the other markets in the table, blind_gate is the one that blocks the sale when the compliance pointer has no gate, and gated_markets includes markets with such a blocker. Called signed in (/mcp/account) for a plan the account has not saved, save_plan gives the my_progress call (start = the coming Monday) that puts it on the user's dashboard. Sanctioned markets are never picked and are flagged. The full answer (default) runs 40,000-80,000 characters; detail=brief keeps the plan and leaves out channel_plan.steps (call channel_plan for endpoint ids, prices and request bodies) and the alternative first-email drafts (first_email_variants, the Japanese ones too), listing what it left out in omitted: use it for a first answer or to compare markets, and the full answer when picking drafts in the weekly routine. The first line names the markets whose replies the data cannot tell apart and why the plan's market comes first (reply multiple, imports, growth, product fit, the prior-consent rule for B2B email), or the one market that is clearly ahead; when country is given and the data would start elsewhere it says so. entry_paths ranks the markets for this product and company (evidence, fit, access, demand per path; markets already selling come first as expansion paths) and ranking says what decided the order and which inputs would change it: pass description, concepts, price_tier and selling_in, or call signed in so the company's certifications, channels and target markets count. plan_url opens the same plan as a one-page web page to print, save as PDF or share (with weekly tracking); ask_next lists the next questions to offer the user. 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": {
      "item": "<item>"
    },
    "name": "gtm_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesProduct 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.
detailNoOptional: brief (about half the size, for chat clients with a result size limit) or full (default, every draft).
originNoOptional: where the product is made, ISO alpha-2 (default KR, or the signed-in company's origin). TradeGraph's reply data comes from Korean exporters: another origin is left out of the markets and origin_check says what applies.
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.
countryNoTarget country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. Optional: omit to let the data pick the market.
excludeNoOptional: markets already tried, comma-separated ISO codes or names (e.g. 'DE,PL'); next_markets skips them.
productNoOptional: the product's own name in English for the first-email draft (e.g. 'kimchi', 'sunscreen'), up to 60 characters. Defaults to the item name; for a live HS code without it the draft says 'products under HS 2005'. A name not in English is not put in the English drafts (product_note says what they use).
conceptsNoOptional: product concepts, comma-separated: halal, vegan, derma, men, kids, organic (premium or mass also set price_tier); halal_certified when the product holds a halal certificate. Also detected from item, product and description. halal ranks Muslim-majority markets ahead among markets that replies cannot tell apart.
strengthsNoOptional: what your company actually offers partners, in English and your own words, up to 240 characters (e.g. 'CE and ISO 9001, 4-week lead time, MOQ 50 units, spare parts stocked in Germany'). The drafts state only this; without it, offers TradeGraph cannot know you make (demo units, training, stock, lead time) stay as [CONFIRM: ...] lines listed in first_email.claims_to_confirm.
price_tierNoOptional: the product's price tier, for market fit (premium favours high-income markets).
selling_inNoOptional: markets where the product already sells (ISO codes or names, e.g. 'US,JP'), from marketplaces or distributors. They become expansion paths ahead of new markets (entry_paths path expand). Also detected from description ('미국 아마존에서 판매 중', 'Shopee SG') and the company's channels.
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).
product_localNoOptional, Japan: the product's name in Japanese for the Japanese drafts (local_emails), e.g. 'カシミヤ混ニット'. A product written in Japanese is used there too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / concepts
      Added value: +{
      +  "description": "Optional: product concepts, comma-separated: halal, vegan, derma, men, kids, organic (premium or mass also set price_tier); halal_certified when the product holds a halal certificate. Also detected from item, product and description. halal ranks Muslim-majority markets ahead among markets that replies cannot tell apart.",
      +  "type": "string"
      +}
    • 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)."
    • addedInput schema / properties / price_tier
      Added value: +{
      +  "description": "Optional: the product's price tier, for market fit (premium favours high-income markets).",
      +  "enum": [
      +    "premium",
      +    "mass"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / selling_in
      Added value: +{
      +  "description": "Optional: markets where the product already sells (ISO codes or names, e.g. 'US,JP'), from marketplaces or distributors. They become expansion paths ahead of new markets (entry_paths path expand). Also detected from description ('미국 아마존에서 판매 중', 'Shopee SG') and the company's channels.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / strengths
      Added value: +{
      +  "description": "Optional: what your company actually offers partners, in English and your own words, up to 240 characters (e.g. 'CE and ISO 9001, 4-week lead time, MOQ 50 units, spare parts stocked in Germany'). The drafts state only this; without it, offers TradeGraph cannot know you make (demo units, training, stock, lead time) stay as [CONFIRM: ...] lines listed in first_email.claims_to_confirm.",
      +  "type": "string"
      +}
    • changedInput schema / properties / traits / description
      Previous value: -"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. Also detected from item, product and description; the answer lists them in product_traits."New value: +"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."
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent safety, and the description carries the rest: it is 'Free, read-only', sanctioned markets are 'never picked and are flagged', the default answer runs 40,000-80,000 characters, and detail=brief changes what is returned and lists it in omitted. It also discloses gating rules (ingredient bans that no approval opens, compliance_gate blocking a market) that an agent could not infer from the schema.

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

Conciseness2/5

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

The purpose is front-loaded well in the first sentence, but the remainder is a dense run-on paragraph with nested parentheticals that repeatedly re-explain return keys with no headers, bullets, or grouping. Content is mostly substantive given there is no output schema, but the packaging makes it hard to scan and pushes well past what an agent can hold in working attention.

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

Completeness5/5

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

With no output schema and 13 parameters, the description takes on the full burden of explaining return values and does so exhaustively: it names and defines first-line market tie-breaking, blind_spots vs blind_spots_by_market vs blind_gate, gated_markets vs banned_markets, reply_target and reply_pace, entry_paths/ranking, plan_url and ask_next. Nothing an agent needs to interpret a call is missing.

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 coverage is 100% and the per-parameter descriptions are already unusually detailed (traits, themes, ISO formats, examples), so the baseline is 3. The description adds scattered consequence-level meaning — strengths governs which draft lines survive as [CONFIRM: ...], exclude is honored by next_markets, detail drops channel_plan.steps and first_email_variants — but most of this is restated from the schema rather than extending it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'One call returns the export go-to-market plan for a product', then enumerates the concrete contents (markets, buyer types, follow-ups, compliance flags, tariffs, drafts, schedule, endpoints). It distinguishes itself from channel_plan and mentions save_plan/my_progress, though it never positions itself against ranking siblings like export_rank or market_picks, so the boundary with those is left implicit.

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?

Strong directive framing with 'START HERE' and explicit mode selection: 'use it for a first answer or to compare markets, and the full answer when picking drafts in the weekly routine'. It also states the signed-in vs. anonymous condition ('Called signed in (/mcp/account) for a plan the account has not saved'). No explicit when-not-to-use or alternative named for market ranking, which keeps it below a 5.

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.