Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_post_comments_post

Retrieve Reddit post details and comments, then paginate comment threads using one opaque cursor.

Instructions

reddit: Post Comments. POST /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_post"
  }
}

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.5/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 load and does well: it discloses single-cursor pagination with no batching, that author flair is unavailable, and a detailed credit-charging model (1 credit on success, 0 on empty comments, errors/cache hits free). It omits auth requirements, rate limits, and any sense of response shape or comment nesting depth.

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 functional content (endpoint, pagination, flair limitation) is front-loaded and efficient. The trailing cost paragraph is boilerplate legalese and slightly self-referential ('charged only where that operation's published cost says so'), diluting an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should compensate by describing what comes back, and it does not beyond the phrase 'post details and comments' — no comment structure, ordering, or pagination-token location. The credit and flair notes help, but an agent still cannot anticipate the response payload.

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 baseline is 3. The description does add genuine meaning for the cursor parameter ('one opaque cursor returned by the previous response', 'do not combine multiple cursors') that the schema only hints at, but 'trim' is left entirely to the schema with no added interpretation.

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 names the endpoint (POST /v1/reddit/post/comments). It partially distinguishes itself from the GET-style sibling by explaining the POST/long-cursor variant, but it never names the alternative tool outright, so the boundary is inferred 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?

It gives a conditional routing hint ('For long cursors, use POST with the same JSON-body parameters') and a pagination rule ('no cursor batching'), which is real usage guidance. However, it never says when to use this versus the plain reddit_post or reddit_post_comments sibling, and the 'use POST' phrasing is ambiguous about whether it refers to this tool or another one.

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