Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_post_comments

Fetch Reddit post details and comments by URL, then paginate through additional comments or replies with an opaque cursor.

Instructions

reddit: Post Comments. GET /v1/reddit/post/comments. Get Reddit post details and comments. Paginate with one opaque cursor; no cursor batching. For long cursors, use POST with the same JSON-body parameters. Author flair is unavailable. Costs 1 credit when it succeeds. Costs 0 credits when comments is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "reddit_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesReddit post URL
trimNoSet true for a trimmed response.
cursorNoOne opaque cursor returned by the previous response to get more comments or replies. Do not combine multiple cursors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses the credit cost on success, zero cost on empty comments, no charge for errors, blocked/timed-out/invalid requests and cache hits, and notes that author flair is unavailable. It omits auth requirements, rate limits, and the shape of the returned payload, but the billing and failure behavior an agent needs before calling is present.

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?

The purpose and endpoint are front-loaded in the first two clauses, followed by pagination and then billing. The billing sentences are dense but each conveys a distinct cost condition; some compression would still help, as the cost enumeration runs long relative to the tool's simplicity.

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 three-parameter read tool with no output schema, the description covers purpose, endpoint, pagination mechanics, a workaround for oversized cursors, and the complete cost model, which is enough to call it correctly. The main gap is the absence of any hint about response contents or ordering, which an agent might want when deciding how to paginate.

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 description coverage is 100%, so url, trim, and cursor are already documented, making the baseline 3. The description adds only marginal meaning beyond the schema: it confirms the cursor is opaque and must not be combined, and notes the POST escape hatch for long cursors. It says nothing about 'trim' beyond what the schema states.

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 description states a specific verb and resource ('Get Reddit post details and comments') and pairs it with the concrete route GET /v1/reddit/post/comments, so the agent knows exactly what is returned. It never names a sibling such as reddit_post or reddit_post_comments_post explicitly, so the differentiation from those tools is left implicit rather than stated.

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?

Pagination guidance is concrete: one opaque cursor, no cursor batching, and switch to POST with the same JSON-body parameters when the cursor is long. However, there is no explicit statement of when to choose this tool over reddit_post (details only) or reddit_post_comments_post, so the when-to-use case against alternatives is only implied by the endpoint and parameter list.

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

Deploy Server

Other Tools