Skip to main content
Glama

TokConnect: TikTok Research

Comment giveaway draw

pick_comment_winners
Read-only

Draws giveaway winners at random from a video's comments, with optional filters (must_include, unique users, exclude the creator). A seed makes the draw reproducible. Reports how many comments were eligible.

Input Schema

NameRequiredDescriptionDefault
seedNoOptional seed for a reproducible draw. Publish it so anyone can re-run the draw.
videoYesPost id or full https://www.tiktok.com/@creator/video/<id> URL.
detailNofull adds TikTok's raw payload (large).compact
winnersNoHow many winners to draw.
max_commentsNoComments to fetch, in pages of 50.
must_includeNoOptional text a comment must contain (case-insensitive), e.g. a hashtag or keyword.
unique_usersNoCount each commenter once (their earliest fetched comment).
exclude_creatorNoExclude comments by the video's creator.

Output Schema

NameRequiredDescriptionDefault
rawNoTikTok's full payload; present only with detail=full.
seedNo
pagesNo
rulesNo
randomNo
awemeIdNo
fetchedNo
winnersNo
coverageNo
eligibleNo
excludedNo
fairnessNo
seedSha256No
totalReportedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "compact",
      +  "description": "full adds TikTok's raw payload (large).",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / exclude_creator / default
      Added value: +true
    • changedInput schema / properties / exclude_creator / description
      Previous value: -"Exclude comments by the video's creator. Defaults to true."New value: +"Exclude comments by the video's creator."
    • addedInput schema / properties / max_comments / default
      Added value: +300
    • changedInput schema / properties / max_comments / description
      Previous value: -"Comments to fetch, 50-500 in pages of 50. Defaults to 300."New value: +"Comments to fetch, in pages of 50."
    • changedInput schema / properties / seed / description
      Previous value: -"Optional seed for a reproducible draw; publish it so anyone can re-run the draw."New value: +"Optional seed for a reproducible draw. Publish it so anyone can re-run the draw."
    • addedInput schema / properties / unique_users / default
      Added value: +true
    • changedInput schema / properties / unique_users / description
      Previous value: -"Count each commenter once (their earliest fetched comment). Defaults to true."New value: +"Count each commenter once (their earliest fetched comment)."
    • changedInput schema / properties / video / description
      Previous value: -"Full https://www.tiktok.com/@creator/video/<id> URL or the numeric video id."New value: +"Post id or full https://www.tiktok.com/@creator/video/<id> URL."
    • addedInput schema / properties / winners / default
      Added value: +1
    • changedInput schema / properties / winners / description
      Previous value: -"How many winners to draw, 1-20. Defaults to 1."New value: +"How many winners to draw."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "awemeId": {
      +      "type": "string"
      +    },
      +    "coverage": {
      +      "type": "number"
      +    },
      +    "eligible": {
      +      "type": "integer"
      +    },
      +    "excluded": {
      +      "type": "object"
      +    },
      +    "fairness": {
      +      "type": "string"
      +    },
      +    "fetched": {
      +      "type": "integer"
      +    },
      +    "pages": {
      +      "type": "integer"
      +    },
      +    "random": {
      +      "type": "string"
      +    },
      +    "raw": {
      +      "description": "TikTok's full payload; present only with detail=full."
      +    },
      +    "rules": {
      +      "type": "object"
      +    },
      +    "seed": {
      +      "type": "string"
      +    },
      +    "seedSha256": {
      +      "type": "string"
      +    },
      +    "totalReported": {
      +      "type": "integer"
      +    },
      +    "winners": {
      +      "items": {
      +        "properties": {
      +          "authorNickname": {
      +            "type": "string"
      +          },
      +          "authorUniqueId": {
      +            "type": "string"
      +          },
      +          "createTime": {
      +            "type": "integer"
      +          },
      +          "diggCount": {
      +            "type": "integer"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "isAuthor": {
      +            "type": "boolean"
      +          },
      +          "text": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "text",
      +          "authorUniqueId",
      +          "authorNickname",
      +          "createTime",
      +          "diggCount",
      +          "isAuthor"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the draw is random, a seed makes it reproducible, and it reports the eligible comment count. It stops short of explaining what happens without a seed (different results each run), which is the crux of the non-idempotent hint.

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?

Three sentences, front-loaded with the core purpose before the filter/seed/reporting details. Every sentence carries distinct information with no waste.

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?

An output schema exists, so return values need not be explained, and the description usefully notes it reports the eligible comment count. For an 8-parameter tool the coverage is adequate, though the absence of any when-to-use routing keeps it short of complete.

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 coverage is 100%, so all eight parameters including filters and seed are already fully documented in the schema. The description names must_include, unique users, exclude creator, and the seed, but restates them rather than adding syntax or format meaning. Baseline 3 applies when the schema does the heavy lifting.

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 verb and resource ('Draws giveaway winners at random from a video's comments'), plus the scoping mechanism (optional filters, seed). An agent can distinguish this from read-only comment tools like video_comments or comment_replies immediately.

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?

Conveys the use case (a giveaway draw) and lists the filters, but never names when to use this instead of video_comments/comment_replies or what conditions make it appropriate. No exclusions or prerequisites are stated, leaving routing to inference.

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