LamaTok — TikTok MCP

get_v1_media_comments_by_id

Read-only

Fetch comments on a TikTok video by ID, one page per call. Set count for page size and cursor to page through results.

Instructions

Get comments on a TikTok video, one page per call. Use get_v1_media_comment_replies_by_id for replies under one comment. Pass the video id; count sets the page size (default 30) and cursor pages through. Live request to TikTok, billed per call. (GET /v1/media/comments/by/id)

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`count`	No
`cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2May 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely new context: 'Live request to TikTok, billed per call' and one-page-per-call pagination behavior. It stops short of rate-limit or return-shape detail, but the cost/billing disclosure is valuable.

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?

Front-loads the core action, then sibling routing, then parameters, then the billing caveat, closing with the raw endpoint. Every sentence earns its place with no filler.

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?

No output schema exists, but annotations cover the safety profile and the description covers parameters, pagination, and billing. It is complete enough for correct invocation, though the id format and count bounds are left to the schema.

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 description coverage is 0%, so the description must carry the burden, and it largely does: it explains id (video id), count (page size, default 30), and cursor (pages through). It omits the 19-digit id format constraint and any bounds on count, so it does not fully compensate.

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 ('Get comments on a TikTok video') and immediately distinguishes itself from the sibling that handles replies. An agent can tell it apart from get_v1_media_comment_replies_by_id without opening either 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?

Explicitly names the alternative tool and the condition that selects it ('Use get_v1_media_comment_replies_by_id for replies under one comment'), and explains how to iterate pages via cursor. The routing decision is fully specified.

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