Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Reddit post

reddit_post_get
Read-onlyIdempotent

Retrieve a Reddit post from a post or share URL to access its content and details. For subreddit-level data, use the subreddit lookup instead.

Instructions

Get a Reddit post by URL. Requires url. url must be a post link (…/r/{subreddit}/comments/{id}/…) or share link (…/r/{subreddit}/s/{id}). For a subreddit, use reddit_subreddit_get.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Reddit post.
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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered without the description. The text adds a useful behavioral constraint beyond annotations — the URL must be a post link or share link — but says nothing about auth, rate limits, or response shape. That is a modest addition over a well-annotated tool.

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: what it does, what input is valid, and which sibling to use otherwise. The routing constraint is front-loaded and nothing is redundant.

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 simple read-only getter with a fully documented 4-parameter schema, the description covers purpose, input validity, and sibling routing. Its one gap is return content: there is no output schema, so the agent is never told whether the response includes post body, score, author, or media, only that it is "a Reddit post."

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 would be 3, but the description adds accepted-format detail the schema lacks: the schema only says "Link to the Reddit post," while the description specifies `/r/{subreddit}/comments/{id}/` or `/r/{subreddit}/s/{id}`. That materially reduces malformed-URL calls. The analytics-only `context`/`llm_model` and the `conversation_id` echo rule are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 a Reddit post") and immediately bounds it with "by URL," plus it names the sibling it is not: "For a subreddit, use `reddit_subreddit_get`." An agent can distinguish this from the subreddit, transcript, and comments siblings without opening any schema.

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

Usage Guidelines4/5

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

It gives explicit routing guidance for the subreddit case ("For a subreddit, use `reddit_subreddit_get`") and pins the accepted input shapes. It does not explicitly rule in/out `reddit_post_transcript_get` or `reddit_post_comments_list`, but those differ by name in an obvious way, so the guidance is clear rather than complete.

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