Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Reddit post comments

reddit_post_comments_list
Read-onlyIdempotent

Lists comments from a Reddit post URL and returns paginated results using a cursor for additional pages.

Instructions

List comments on a Reddit post by URL. Requires url. Returns a list (use cursor when paginated). Pass the post link in url (…/r/{subreddit}/comments/{id}/…); a bare post id is not accepted and there is no id field.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "reddit_post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Reddit post.
trimNoWhen true, requests a lighter response shape when available.
cursorNoOpaque cursor from a previous response to fetch another page of comments or replies.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context that it returns a list and uses a cursor for pagination, though it does not mention rate limits or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences are front-loaded with purpose, then constraints and return behavior. The wording is efficient and no sentence is wasted.

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?

There is no output schema, but the description states that it returns a list and how pagination works via cursor. Other parameters are fully documented in the schema, so the definition is complete enough for a simple list operation.

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%, so the baseline is 3. The description adds meaningful semantics beyond the schema for the critical url parameter by requiring a full post link and rejecting bare ids, and it clarifies cursor use for pagination.

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?

States a specific verb and resource: "List comments on a Reddit post by URL." The scope is clear and distinguishable from fetching the post itself, but it does not explicitly name sibling alternatives.

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?

Gives an important calling constraint: pass the full post link and not a bare post id. It does not explain when to use this tool instead of reddit_post_get or other comment-list alternatives, nor when not to use it.

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