Export GTM plan for a product
gtm_planSTART 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
| Name | Required | Description | Default |
|---|---|---|---|
| item | Yes | Product 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. | |
| detail | No | Optional: brief (about half the size, for chat clients with a result size limit) or full (default, every draft). | |
| origin | No | Optional: 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. | |
| traits | No | 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. | |
| country | No | Target 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. | |
| exclude | No | Optional: markets already tried, comma-separated ISO codes or names (e.g. 'DE,PL'); next_markets skips them. | |
| product | No | Optional: 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). | |
| concepts | No | 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. | |
| strengths | No | 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. | |
| price_tier | No | Optional: the product's price tier, for market fit (premium favours high-income markets). | |
| selling_in | No | 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. | |
| description | No | 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). | |
| product_local | No | Optional, Japan: the product's name in Japanese for the Japanese drafts (local_emails), e.g. 'カシミヤ混ニット'. A product written in Japanese is used there too. |