Skip to main content
Glama

Vee3

by io.github.Vee3io

tiktok.comment_replies

List replies to a TikTok comment. Requires video_id and comment_id. Pass cursor from a previous response to fetch the next page.

Cost = 2 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of replies to return (max 40).
cursorNoPagination cursor from a previous response.
video_idYesTikTok video id.
comment_idYesTikTok comment id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
msgNoUpstream status message.
codeNoUpstream status code (0 = success).
dataNoCapability-specific payload from the upstream provider.
processed_timeNoUpstream processing time in seconds.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / properties / processed_time / anyOf
      Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that this is a listing operation, spells out required inputs, mentions pagination via cursor, and adds the non-obvious cost of 2 tokens. It could also state that it's read-only, but 'List' already implies that.

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 short sentences, each directly informative: purpose, required params, pagination, and cost. No wasted words, properly front-loaded.

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 simple list tool with full schema coverage and an output schema, the description covers all essential aspects: what it does, required inputs, pagination behavior, and cost. There are no notable gaps given the low complexity.

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 the schema documents all parameters. The description only repeats what the schema already says about cursor and required parameters, adding no new semantics or syntax details beyond the structured data.

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?

The description uses a specific verb ('List') and resource ('replies to a TikTok comment'), clearly distinguishing it from sibling tools like tiktok.video_comments. It also names the two required parameters, making the tool's scope unambiguous.

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?

The description provides clear context: it requires video_id and comment_id, and explains cursor-based pagination for fetching subsequent pages. However, it does not explicitly mention alternatives or when not to use the tool, so it misses the 'when-not/exclusions' part for a 5.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources