Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

List Reddit post comments

reddit_post_comments_list
Read-only

List comments on a Reddit post by URL. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesLink 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 (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never 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. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "context",
+  "llm_model"
+]
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Link to the Reddit post whose comments should be listed. Accepts post URLs (…/comments/…) or share URLs (…/s/…). Relative `/r/…` paths are rewritten to https://www.reddit.com."New value: +"Link to the Reddit post."
  4. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Link to the Reddit post whose comments should be listed."New value: +"Link to the Reddit post whose comments should be listed. Accepts post URLs (…/comments/…) or share URLs (…/s/…). Relative `/r/…` paths are rewritten to https://www.reddit.com."
  5. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  6. Changed1 schema field changed
    • changedInput schema / properties / trim / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  }
-]New value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "enum": [
+      "0",
+      "1",
+      "true",
+      "false"
+    ],
+    "type": "string"
+  }
+]
  7. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds the useful behavioral detail that the tool returns a paginated list and that the cursor parameter should be used for further pages. This is meaningful but not rich; no mention of rate limits, result shape, or whether replies are included.

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?

Two short sentences: the first states the core purpose, and the second adds the key pagination behavior. No filler words, front-loaded, and every phrase earns its place.

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?

For a simple read-only list tool, the description is minimally viable: it names the input, output type, and pagination. However, with no output schema, it does not describe the shape of the comment list (e.g., author, text, replies) nor any sorting or limit behavior, which would help an agent know what to expect from the result.

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 each parameter is already documented. The description adds little beyond noting the URL as the primary input and cursor for pagination; it does not compensate with additional semantic detail beyond the schema, so the baseline 3 holds.

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 clearly states the verb ('List'), the resource ('comments on a Reddit post'), and the identifying input ('by URL'). It is unambiguous among the many platform-specific comment list tools, though it does not explicitly differentiate itself from siblings like reddit_post_get or reddit_post_transcript_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives such as reddit_post_get or reddit_post_transcript_get. The only usage hint is the pagination note ('use cursor when paginated'), which is about mechanics rather than tool selection. There are no exclusions or alternative conditions stated.

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

All Social Fetch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.

Naming Consistency5/5

All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).

Tool Count2/5

The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.

Completeness4/5

The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.

Resources