Skip to main content
Glama
Sign In

TokConnect: TikTok Research

by com.tokconnect.mcp
OverviewDiscussionsAdmin

One TikTok creator

creator
Read-onlyIdempotent

One creator's public account: profile (followers, likes, bio, Shop seller status; counts are rounded the way the app shows them, so use creator_search with the handle for exact numbers), posts, reposts, liked posts, followers, following, embed posts, playlists and collections. Pass any identifier; TokConnect resolves the ids. For what the creator sells or earns, the products they link, or their follower demographics, use creator_commerce. Example: {"id":"@dollskill","method":"posts"}. method=audit reports the account's registered country, ids and TikTok's milestones (started posting, follower marks); method=lookalikes lists accounts TikTok suggests as similar. Example: {"id":"@nike","method":"audit"}.

Input Schema

NameRequiredDescriptionDefault
idYesCreator: @handle, profile or video link, secUid (MS4wLjAB...) or numeric user id. TokConnect looks up the ids it needs.
limitNoResults per page. posts max 35, others max 30. Values above a method's maximum are lowered and reported in notes.
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. profile: followers, likes, videos, bio, link, verified, Shop seller, ids | posts: posts, newest first, with counts and linked products | reposts: posts the creator reposted | likes: public Liked tab (empty when hidden) | followers: followers, when TikTok shows them (usually hidden) | following: accounts followed, when shown (usually hidden) | embed: posts in the creator's embed widget | playlists: public playlists (ids for creator_playlist) | collections: public saved collections (often empty) | audit: registered country, ids, TikTok milestones (started posting, follower marks) | lookalikes: accounts TikTok suggests as similarprofile
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.

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. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page. posts max 35, stories max 10, others max 30. Values above a method's maximum are lowered and reported in notes."New value: +"Results per page. posts max 35, others max 30. Values above a method's maximum are lowered and reported in notes."
    • changedInput schema / properties / method / description
      Previous value: -"What to get. profile: followers, likes, videos, bio, link, verified, Shop seller, ids | posts: posts, newest first, with counts and linked products | reposts: posts the creator reposted | likes: public Liked tab (empty when hidden) | stories: Stories up now (they expire) | followers: followers, when TikTok shows them (usually hidden) | following: accounts followed, when shown (usually hidden) | embed: posts in the creator's embed widget | playlists: public playlists (ids for creator_playlist) | collections: public saved collections (often empty)"New value: +"What to get. profile: followers, likes, videos, bio, link, verified, Shop seller, ids | posts: posts, newest first, with counts and linked products | reposts: posts the creator reposted | likes: public Liked tab (empty when hidden) | followers: followers, when TikTok shows them (usually hidden) | following: accounts followed, when shown (usually hidden) | embed: posts in the creator's embed widget | playlists: public playlists (ids for creator_playlist) | collections: public saved collections (often empty) | audit: registered country, ids, TikTok milestones (started posting, follower marks) | lookalikes: accounts TikTok suggests as similar"
    • changedInput schema / properties / method / enum
      Previous value: -[
-  "profile",
-  "posts",
-  "reposts",
-  "likes",
-  "stories",
-  "followers",
-  "following",
-  "embed",
-  "playlists",
-  "collections"
-]New value: +[
+  "profile",
+  "posts",
+  "reposts",
+  "likes",
+  "followers",
+  "following",
+  "embed",
+  "playlists",
+  "collections",
+  "audit",
+  "lookalikes"
+]
    • addedInput schema / properties / region
      Added value: +{
+  "description": "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.",
+  "maxLength": 2048,
+  "type": "string"
+}
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Well beyond the annotations, which only declare read-only/idempotent/open-world: it discloses that counts are rounded the way the app shows them, that likes/followers/following are frequently hidden or empty, that over-limit values are silently lowered and reported in notes, and that unsupported regions are refused. These are real behavioral caveats an agent would otherwise hit at runtime.

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 its contents, then constraints, then routing, then examples — a sensible order. It runs long and the two JSON examples plus the audit/lookalikes sentence partly restate what the method enum already documents, which is the main slack.

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?

For a six-parameter, eleven-method tool with an output schema, the description covers the meaningful gaps: multiplier caveats on hidden data, rounding, region refusal, id resolution, and method selection. Pagination and limits are fully described in the schema, so nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds value by explaining the identifier resolution behavior and expanding on the non-obvious methods (audit, lookalikes) with concrete call examples. The method and region semantics largely live in the enum descriptions, so this is additive rather than essential.

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?

Opens with a specific resource scope — one creator's public account — and enumerates exactly which artifacts come back (profile, posts, reposts, likes, followers, following, playlists, collections). It also names two sibling tools with the conditions that route away from it, so an agent can separate it from creator_search and creator_commerce without opening a schema.

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?

Gives explicit routing rules with conditions: use creator_search with the handle for exact (unrounded) counts, and use creator_commerce for what the creator sells, earns, links, or their follower demographics. It also states the identifier policy ('Pass any identifier; TokConnect resolves the ids'), removing a common pre-call question.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TokConnect: TikTok Research toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources