LamaTok — TikTok MCP

get_v1_media_comment_replies_by_id

Read-only

Retrieve paginated replies under a TikTok video comment using media_id and comment_id; set count and cursor to read through the thread.

Instructions

Get replies under one comment of a TikTok video, one page per call. Use it to read a thread; use get_v1_media_comments_by_id for the top-level comments. Pass media_id and comment_id (both from the comments tool); count sets the page size and cursor pages through. Live request to TikTok, billed per call. (GET /v1/media/comment/replies/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": {
      "media_id": "<media_id>",
      "comment_id": "<comment_id>"
    },
    "name": "get_v1_media_comment_replies_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No
`cursor`	No
`media_id`	Yes
`comment_id`	Yes

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 readOnly, non-destructive, and open-world. The description adds meaningful context beyond that: one page per call, cursor-based pagination, and that this is a live TikTok request billed per call. Rate limits and error behavior remain unstated, keeping it short of a 5.

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 purpose, then sibling routing, then parameter roles and the billing caveat. No redundant or filler sentences; every clause earns its place.

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 no output schema, the description still conveys pagination behavior and per-call billing, which is enough to invoke it correctly. Return-shape specifics are absent but a paged read tool rarely needs them spelled out.

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 0%, so the description carries the burden, and it does well: media_id and comment_id are sourced from the comments tool, count is the page size, cursor pages through. It omits the 19-digit pattern constraint, but that lives in 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?

States a specific verb and resource: 'Get replies under one comment of a TikTok video.' It explicitly distinguishes itself from the sibling top-level comments tool, so an agent can route correctly 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?

Gives explicit when-to-use ('read a thread') and names the alternative ('use get_v1_media_comments_by_id for the top-level comments'). It also explains where the required IDs come from (the comments tool), removing ambiguity about prerequisites.

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