Skip to main content
Glama

Channels, creators and live-data calls for a country

channel_plan
Read-onlyIdempotent

GTM engineering plan for one country: creator platforms to seed on, marketplaces to research, buyer channels, local-language and disclosure rules, product compliance pointers (with an official source link), the official tariff lookup and Korea FTA, and the treg.to endpoint ids (with per-call prices and example request bodies) to run creator discovery, vetting, marketplace research, social listening, ad-library and buyer-contact steps. Estimated data cost included.

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": "channel_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
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; adds niche keywords and compliance pointers.
motionNoWhich part of the plan to return. 'all' adapts to the item: industrial goods get b2b, trade and search only.
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.
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).

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. Changed1 schema field changed
    • 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

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds value by disclosing what the response contains: per-call endpoint prices, example request bodies, an estimated data cost, and an official source link. That cost/scope disclosure is genuinely useful for an agent deciding whether to call it, though it does not discuss response size or latency.

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 whole definition is one long run-on sentence with a heavy comma-separated inventory. Every clause carries information, yet the density makes it harder to parse than a short lead plus a structured list would be.

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?

There is no output schema, so the description must convey returns, and it does: plan sections, endpoint ids with prices, example bodies, cost estimate and a compliance source link. Combined with full schema coverage on all five parameters, an agent has enough to call it correctly; only the absence of sizing/routing cues keeps it from a 5.

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 the schema already documents country, item, motion and traits in depth. The description's enumeration of plan sections loosely maps to the 'motion' values but adds no format, defaulting or interplay rules beyond what the schema states — the baseline 3 applies.

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?

The description names a specific deliverable — a GTM plan scoped to one country — and enumerates its concrete contents (creator platforms, marketplace research, tariff lookup, FTA, treg.to endpoint ids with prices). An agent can tell what it produces, but nothing distinguishes it from close siblings like gtm_plan or country_brief, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: if you need a country-scoped channel/creator plan with cost estimates, this is the tool. There is no explicit when-to-use, when-not-to-use, or routing away from gtm_plan, country_brief or market_picks, which is a real gap given the crowded sibling set.

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.