Skip to main content
Glama

TokConnect: TikTok Research

TikTok Shop category trends

category_trends
Read-onlyIdempotent

[Shop Analytics] The top TikTok Shop categories by estimated revenue over the last 7 days of data: revenue, units, growth, revenue per shop, top-3 and top-10 shop share, split by video, LIVE and affiliate. method=tree lists category names and ids (pass them as category to product_top_selling or creator_top_selling); method=products gives a category's top product ids; method=market_size counts what Shop Analytics tracks in a market, not all of TikTok Shop. region picks the market (default US). Example: {"method":"tree","keyword":"skincare"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "category_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoShop Analytics methods: custom range end, YYYY-MM-DD (capped at the last complete day).
levelNomethod=list or tree: keep only categories of this level (1 = top level, 3 = most specific).
limitNomethod=tree: max categories to return (default 50).
startNoShop Analytics methods: custom range start, YYYY-MM-DD.
detailNocompact (default) returns the useful fields; full adds the full raw record (large).compact
methodNoWhat to get. list [Shop Analytics]: categories with revenue, growth and concentration | products [Shop Analytics]: a category's top product ids (US market only) | search [Shop Analytics]: find category names and ids by keyword | tree: category names and ids to use as category | market_size [Shop Analytics]: how many products, shops, creators, videos, LIVEs and brands Shop Analytics trackslist
regionNoMarket as an ISO country code, default US. Shop Analytics methods: sales data for that market, amounts in its currency. Live methods that take it (search, video detail, creator posts, Shop pages): TikTok as seen in that market where TikTok serves it. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. See shop_regions.
windowNoShop Analytics methods: date range ending at the last complete day (about 2 days ago). Default 30d. Use start/end for a custom range.
keywordNomethod=search: category name to look up, e.g. 'serum'. method=tree: text to find in category names, e.g. 'skincare'.
categoryNomethod=products: category name exactly as method=list returns it (cate_id), e.g. 'Beauty & Personal Care'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"compact (default) returns the useful fields; full adds the raw upstream payload (large)."New value: +"compact (default) returns the useful fields; full adds the full raw record (large)."
    • changedInput schema / properties / keyword / description
      Previous value: -"method=search: category name to look up in the data source, e.g. 'serum'. method=tree: text to find in category names, e.g. 'skincare'."New value: +"method=search: category name to look up, e.g. 'serum'. method=tree: text to find in category names, e.g. 'skincare'."
    • changedInput schema / properties / method / description
      Previous value: -"What to get. list [Shop Analytics]: categories with revenue, growth and concentration | products [Shop Analytics]: a category's top product ids (US market only) | search [Shop Analytics]: find category names and ids by keyword | tree: category names and ids to use as category | market_size [Shop Analytics]: how many products, shops, creators, videos, LIVEs and brands the source tracks"New value: +"What to get. list [Shop Analytics]: categories with revenue, growth and concentration | products [Shop Analytics]: a category's top product ids (US market only) | search [Shop Analytics]: find category names and ids by keyword | tree: category names and ids to use as category | market_size [Shop Analytics]: how many products, shops, creators, videos, LIVEs and brands Shop Analytics tracks"
  2. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"Shop Analytics methods: market as an ISO country code, default US. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. Amounts are in the market's currency. See shop_regions."New value: +"Market as an ISO country code, default US. Shop Analytics methods: sales data for that market, amounts in its currency. Live methods that take it (search, video detail, creator posts, Shop pages): TikTok as seen in that market where TikTok serves it. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. See shop_regions."
  3. Changed6 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"method=search: category name to look up, e.g. 'serum'."New value: +"method=search: category name to look up in the data source, e.g. 'serum'. method=tree: text to find in category names, e.g. 'skincare'."
    • changedInput schema / properties / level / description
      Previous value: -"method=list: keep only categories of this level (1 = top level, 3 = most specific)."New value: +"method=list or tree: keep only categories of this level (1 = top level, 3 = most specific)."
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "method=tree: max categories to return (default 50).",
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / method / description
      Previous value: -"What to get. list [Shop Analytics]: categories with revenue, growth and concentration | products [Shop Analytics]: a category's top product ids | search [Shop Analytics]: find category names and ids by keyword"New value: +"What to get. list [Shop Analytics]: categories with revenue, growth and concentration | products [Shop Analytics]: a category's top product ids (US market only) | search [Shop Analytics]: find category names and ids by keyword | tree: category names and ids to use as category | market_size [Shop Analytics]: how many products, shops, creators, videos, LIVEs and brands the source tracks"
    • changedInput schema / properties / method / enum
      Previous value: -[
      -  "list",
      -  "products",
      -  "search"
      -]New value: +[
      +  "list",
      +  "products",
      +  "search",
      +  "tree",
      +  "market_size"
      +]
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Shop Analytics methods: market as an ISO country code, default US. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. Amounts are in the market's currency. See shop_regions.",
      +  "maxLength": 2048,
      +  "type": "string"
      +}
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, and open-world, so the safety burden is low. The description adds useful behavioral caveats about market_size scope and region default, but its opening claim of 'last 7 days of data' conflicts with the schema's default window of 30d, which is a notable transparency gap.

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

Conciseness5/5

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

The purpose and method breakdown are front-loaded, and the example is placed at the end for illustration. Despite covering multiple methods and conditional behaviors, every sentence carries useful information without unnecessary repetition.

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?

Given the 10 parameters, multiple method modes, rich schema coverage, annotations, and an output schema, the description is largely complete: it explains method routing, region behavior, and a key scope caveat. The only material gap is the 7-day framing versus the 30d default window.

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 all 10 parameters in detail. The description repeats method meanings and adds an example, but the 'last 7 days' phrasing contradicts the schema's 30d default window, so it does not add reliable semantics beyond the schema.

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 resource and metric (top TikTok Shop categories by estimated revenue with revenue, units, growth, and shop-share splits) and clearly enumerates what each method returns. It also distinguishes itself from sibling tools by explaining how category ids from method=tree are passed to product_top_selling or creator_top_selling.

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 explicitly routes between methods: tree for category ids, products for a category's top products, and market_size for tracked-entity counts. It names downstream alternatives and clarifies that market_size counts what Shop Analytics tracks rather than all of TikTok Shop.

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.

Resources