PostToData

Comments

get_comments

Read-only

The replies under one post, flattened with depth. Returns compact, cited results (each item has a url). Works on: bluesky, hackernews, youtube, reddit, x, tiktok, instagram, threads, xiaohongshu, douyin. Requires a prepaid API key.

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": {
      "platform": "<platform>",
      "id": "<id>"
    },
    "name": "get_comments"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Post ID, or the public URL of the post.
`limit`	No	Items to return, 1 to 50. Default 10.
`platform`	Yes	Which platform to read. Live now: Bluesky, Hacker News, YouTube, Reddit, X (Twitter), TikTok, Instagram, Threads, Xiaohongshu (RedNote), Douyin.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only cover read-only and open-world; the description adds real behavior: results are flattened but retain depth, each item carries a source url for citation, and a prepaid API key is required. Return-shape and auth details go beyond the annotations, though pagination/thread-limit behavior is still unstated.

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?

Three short, front-loaded sentences: purpose first, output shape second, support/auth third. The platform enumeration partially duplicates the schema enum, which is minor redundancy in an otherwise tight description.

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 does the necessary work of sketching the return value (compact cited items with urls, flattened with depth). Given a simple three-parameter read tool, only detail on thread depth limits or pagination is missing.

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 platform, id, and limit are already fully documented in the input schema. The description's mention of "one post" and the platform list restates what the schema and enum already convey, adding little new meaning to parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"The replies under one post, flattened with depth" names the resource (replies/comments of a single post) and the shape of the result, so an agent can distinguish it from get_post or get_user_posts. It does not explicitly contrast itself with those siblings, which keeps it short of a 5.

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?

Usage is implied: call it with a platform and a post id to read the reply thread. The platform availability list and the prepaid API key prerequisite are useful preconditions, but there is no explicit "use this instead of X" or when-not guidance.

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

All PostToData 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?