Skip to main content
Glama

TokConnect: TikTok Research

One TikTok Shop seller

shop
Read-onlyIdempotent

Everything about one TikTok Shop seller (id = sellerId, found on any of its products, or with shop_top_selling keyword=). Live: store (what shoppers see: rating, followers, catalogue). [Shop Analytics, any market via region]: sales (revenue, units, affiliate vs own vs mall), trend (daily), products, new_products, strategy (pricing, top affiliates unnamed), creators, videos, new_affiliates and affiliate_videos (daily counts with summary). Example: {"id":"7495514739648989419","method":"new_affiliates","window":"30d"}.

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": {
      "id": "<id>"
    },
    "name": "shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSeller id (sellerId on products and stores).
endNoShop Analytics methods: custom range end, YYYY-MM-DD (capped at the last complete day).
slugNomethod=store: store slug if known; looked up when omitted.
limitNoResults per page. Shop Analytics methods max 100. Values above a method's maximum are lowered and reported in notes.
startNoShop Analytics methods: custom range start, YYYY-MM-DD.
cursorNoPaging: pass the next value from the previous response unchanged. Omit on the first page.
detailNocompact (default) returns the useful fields; full adds the full raw record (large).compact
methodNoWhat to get. store: live storefront: rating, sold, followers, products | sales [Shop Analytics]: revenue and units, split by own accounts, affiliates and mall | trend [Shop Analytics]: daily revenue and units (up to ~13 months) | products [Shop Analytics]: its products ranked by revenue | new_products [Shop Analytics]: products it launched in the window | strategy [Shop Analytics]: price bands and sales-channel mix: top affiliates (individuals unnamed) and the shop's own accounts | creators [Shop Analytics]: affiliate creators selling for it, with revenue | videos [Shop Analytics]: videos selling its products, with revenue | new_affiliates [Shop Analytics]: daily count of new affiliates who started promoting the shop, with a summary | affiliate_videos [Shop Analytics]: daily count of new videos affiliates posted for the shop, with a summarystore
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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)."
  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. Changed3 schema fields changed
    • changedInput schema / properties / method / description
      Previous value: -"What to get. store: live storefront: rating, sold, followers, products | sales [Shop Analytics]: revenue and units, split by own accounts, affiliates and mall | trend [Shop Analytics]: daily revenue and units (up to ~13 months) | products [Shop Analytics]: its products ranked by revenue | new_products [Shop Analytics]: products it launched in the window | strategy [Shop Analytics]: price bands and sales-channel mix (affiliate vs own accounts) | creators [Shop Analytics]: affiliate creators selling for it, with revenue | videos [Shop Analytics]: videos selling its products, with revenue"New value: +"What to get. store: live storefront: rating, sold, followers, products | sales [Shop Analytics]: revenue and units, split by own accounts, affiliates and mall | trend [Shop Analytics]: daily revenue and units (up to ~13 months) | products [Shop Analytics]: its products ranked by revenue | new_products [Shop Analytics]: products it launched in the window | strategy [Shop Analytics]: price bands and sales-channel mix: top affiliates (individuals unnamed) and the shop's own accounts | creators [Shop Analytics]: affiliate creators selling for it, with revenue | videos [Shop Analytics]: videos selling its products, with revenue | new_affiliates [Shop Analytics]: daily count of new affiliates who started promoting the shop, with a summary | affiliate_videos [Shop Analytics]: daily count of new videos affiliates posted for the shop, with a summary"
    • changedInput schema / properties / method / enum
      Previous value: -[
      -  "store",
      -  "sales",
      -  "trend",
      -  "products",
      -  "new_products",
      -  "strategy",
      -  "creators",
      -  "videos"
      -]New value: +[
      +  "store",
      +  "sales",
      +  "trend",
      +  "products",
      +  "new_products",
      +  "strategy",
      +  "creators",
      +  "videos",
      +  "new_affiliates",
      +  "affiliate_videos"
      +]
    • 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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds the meaningful split that 'store' is live shopper-facing data while the other methods are Shop Analytics and market-dependent via region. It also discloses that strategy data leaves individual affiliates unnamed, which is behavioral context the schema does not convey.

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

Conciseness4/5

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

Front-loaded with the resource and the id-resolution hint, then the method inventory, then an example. Dense but every clause carries information; the inline method enumeration is long but justified for a 10-method multi-purpose tool.

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?

With an output schema, full annotation coverage and 100%-documented parameters, the description only needs to orient the agent, which it does. Minor gaps remain: paging via cursor and the compact/full detail tradeoff are only in the schema, not reinforced here.

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% and the method enum already carries per-value explanations, so the description's method list largely restates structured data. The one added element is a concrete example invocation showing id + method + window together, which is helpful but marginal against an already complete 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?

States a specific resource and scope ('Everything about one TikTok Shop seller') and immediately enumerates the two families of data available (live storefront vs Shop Analytics methods). It also tells the agent how the required id is obtained and names siblings (shop_top_selling, shop_regions), so it is distinguishable without opening the 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?

Gives explicit guidance for the required id (found on products, or via shop_top_selling with keyword=<shop name>) and points to shop_regions for market support, with the constraint that unsupported countries are refused. It does not explicitly contrast this tool with shop_browse, but the method list makes the intended context clear.

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