ShortsIntel

Get a video's comments

get_comments

Use when you need what viewers say about one video: a page of its comments (text, likes, reply count, never the author), with analyze its sentiment and themes. Not for one comment's thread: use get_comment_replies. Not for the video itself: use get_video. Price: 3 credits per page; +10 credits with analyze. By URL or platform + id, on TikTok, Instagram, YouTube or Facebook. limit 1-100 (default 25); pass next_cursor as cursor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_comments"
  }
}

Input Schema

Name	Required	Description
`id`	No	The platform's own video id
`url`	No	TikTok, Instagram, YouTube or Facebook video URL. Pass this or platform + id
`limit`	No
`cursor`	No	next_cursor from a previous get_comments for the same video, for the next page.
`analyze`	No	Add a sentiment distribution and themes for the surcharge
`estimate`	No	Quote the price in Credits: no Run, no charge
`platform`	No
`max_credits`	No
`idempotency_key`	No	Reuse on a retry: replays the original Run, not charged again

Output Schema

Name	Required	Description	Default
`run`	No
`cached`	No
`result`	No
`poll_url`	No
`estimate_credits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026

changedInput schema / properties / estimate / description

Previous value: -"Return the price, in Credits, without running the operation or creating a Run"New value: +"Quote the price in Credits: no Run, no charge"

changedInput schema / properties / idempotency_key / description

Previous value: -"Reuse the same key when retrying: a repeat returns the original Run and is not charged again"New value: +"Reuse on a retry: replays the original Run, not charged again"

changedOutput schema / properties / run / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / run / properties
```
Removed value: -{}
```

Changed1 schema field changedNov 4, 2026
- addedInput schema / properties / max_credits
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```
Changed1 schema field changedNov 4, 2026
- addedOutput schema / properties / poll_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "cached": {
+      "type": "boolean"
+    },
+    "estimate_credits": {
+      "type": "integer"
+    },
+    "result": {
+      "$ref": "#/properties/run"
+    },
+    "run": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations it discloses the credit cost (3 per page, +10 with analyze), the surcharge semantics of the analyze flag, and that author identity is never returned — genuine behavioral context the annotations do not carry. It stops short of covering failure modes, rate limits, or whether credits are consumed on empty results, so it is strong but not exhaustive.

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-loads the selection condition and packs pricing, platforms, and pagination into a few dense lines with no filler. The phrase 'with analyze its sentiment and themes' is grammatically broken and momentarily ambiguous, which costs it a point.

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?

For a 9-parameter, credit-metered tool with an output schema (so return shape needn't be described), it covers the decision-relevant facts: when to use, cost, platforms, and paging. The pricing-related parameters max_credits and estimate are left entirely to the schema, so an agent must still read the schema to understand budget capping.

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?

With 67% schema coverage the schema already documents url, id, cursor, analyze, estimate, and idempotency_key; the description adds real value by stating the limit range and default (1-100, default 25) and by clarifying that next_cursor is passed as cursor. It omits the credit-cap and idempotency semantics beyond what the schema says.

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 ('a page of its comments') plus the exact fields returned and the explicit exclusion ('never the author'), and names the sibling tools it is not (get_comment_replies, get_video) so it is distinguishable without opening any 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?

Opens with an explicit 'Use when' condition and supplies two negative routings with the correct alternatives, plus the supported platforms and the cursor-pagination contract. An agent can pick this tool versus its siblings and page it correctly from the description alone.

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

All ShortsIntel tools Inspect

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

Need Help?