Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Reddit subreddit

reddit_subreddit_get
Read-onlyIdempotent

Retrieve details for a Reddit community by subreddit name or URL, providing the community information needed to inspect or analyze the subreddit.

Instructions

Get details for a Reddit community (subreddit). Optional inputs: subreddit and url.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional subreddit URL for the request.
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.
subredditNoSubreddit name, optional `r/` prefix, or Reddit subreddit URL. Must match Reddit's exact casing.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that — it does not say what happens when both `subreddit` and `url` are supplied, nor what occurs when neither is provided (both are optional, so this is a real behavioral gap).

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?

Two short sentences with the purpose front-loaded; nothing is padded. The second sentence is largely redundant with the schema, which keeps it from a 5.

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?

This is a simple read-only lookup with rich annotations, fully documented parameters, and no output schema, so the description is nearly sufficient. The unresolved ambiguity — how `subreddit` and `url` interact and what happens if neither is given — is the one thing an agent would want stated.

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 the baseline is 3. The description enumerates `subreddit` and `url` but adds no format, precedence, or fallback semantics beyond what the schema already documents for those two fields.

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 — 'Get details for a Reddit community (subreddit)' — which is clearly distinct from sibling list tools like reddit_subreddit_posts_list and reddit_subreddit_search_list. It stops short of naming any sibling explicitly, but the read-one-entity framing is unambiguous.

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 when-to-use guidance, no exclusions, and no prerequisites are given. The only usage-adjacent statement is 'Optional inputs: `subreddit` and `url`', which restates schema structure rather than telling the agent when to pick this tool over reddit_subreddit_search_list or reddit_post_get.

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