Skip to main content
Glama
Sign In

Perkadoo

by com.perkadoo
OverviewDiscussionsAdmin

Read a post's comments from its link

read_post_comments
Read-onlyIdempotent

Read every top-level comment on a public post from its link, with no account: YouTube videos, Bluesky posts and Reddit threads (where this server has a Reddit app). Returns the post (title, the account that posted it) and each comment's handle, text and time, ready for draw_winners or a comment picker. An Instagram post needs its owner: the answer is a link for them to pick a verifiable winner from that post.

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": {
      "link": "<link>"
    },
    "name": "read_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe post's link, as copied from its share button: a YouTube video, a Bluesky post or a Reddit thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / link / description
      Previous value: -"The post's link, as copied from its share button: a YouTube video."New value: +"The post's link, as copied from its share button: a YouTube video, a Bluesky post or a Reddit thread."
  2. Changed1 schema field changed
    • changedInput schema / properties / link / description
      Previous value: -"The post's link, as copied from its share button: a YouTube video or a Bluesky post."New value: +"The post's link, as copied from its share button: a YouTube video."
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, yet the description adds real context beyond them: 'with no account' (no auth needed), 'top-level comment' scoping (replies excluded), the Reddit-app prerequisite, and the Instagram owner constraint. It stops short of covering limits on large threads or pagination behavior, so not 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded, but the final Instagram sentence is a long, syntactically tangled aside ('the answer is a link for them to pick a verifiable winner from that post') that costs the reader more than it returns. The middle return-shape sentence is efficient.

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 carries the burden of describing returns and does so adequately — post title, posting account, and each comment's handle, text and time. The one gap is what happens for very large threads or unsupported links, which stays unclear.

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 100% and the single `link` parameter is already documented, so baseline is 3. The description earns a bump by adding the platform constraint (which links are valid) and the Instagram exception, which is usage-relevant meaning the schema alone does not convey.

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?

Opens with a specific verb and resource: 'Read every top-level comment on a public post from its link,' and names the supported platforms (YouTube, Bluesky, Reddit). The closing Instagram sentence is muddled — it is unclear whether Instagram is supported at all or merely returns a URL — which slightly blurs the scope the first sentence establishes.

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?

Implies downstream usage ('ready for draw_winners or a comment picker') rather than stating when to call this versus a sibling. The only explicit conditional is the Instagram/owner caveat, and no sibling tool is named as an alternative for unsupported platforms.

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

All Perkadoo toolsInspect
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