Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Find other discussions of a post or link

find_other_discussions
Read-onlyIdempotent

Find crossposts and other Reddit threads that discuss the same link or URL. Enter a Reddit post ID/URL to locate crossposts, or an article, repo, or video URL to find threads linking it.

Instructions

Find Reddit threads about the same link.

Given a Reddit post: its crossposts and other submissions of the same URL. Given an article, repo or video URL: the threads that submitted it (Reddit matches the URL exactly; one variant with or without the trailing slash is tried automatically).

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": {
      "post_or_url": "<post_or_url>"
    },
    "name": "find_other_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults, 1 to 100.
post_or_urlYesA Reddit post (id or URL) for its crossposts, or any external URL for threads that link it.
include_nsfwNoShow posts, comments and communities Reddit marks NSFW (18+). Off by default; hidden items are counted in the output. A server setting can keep them hidden even when true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile needs no restatement. The description contributes beyond them by disclosing the exact-URL matching constraint and the automatic trailing-slash retry — a real behavioral limitation an agent should know before concluding 'no results means no discussion'.

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, front-loaded with the one-line purpose before the two input branches. Every sentence carries non-redundant information; there is no restatement of the title or the schema.

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?

With no output schema, the description does the job of saying what comes back in each mode (crossposts/other submissions vs. submitting threads), which is the key unknown. It does not describe result ordering or how the limit interacts with the two modes, a minor gap for a three-parameter read tool whose safety semantics are already covered by annotations.

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, but the description adds real semantics the schema only implies: it clarifies that post_or_url is polymorphic by design and that Reddit matches the URL exactly, with one trailing-slash variant auto-retried. That matching rule is troubleshooting information the schema does not convey, which lifts it above baseline.

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 opening line states a specific verb and resource (find Reddit threads about the same link) and then splits the behavior by input type: a Reddit post yields crossposts and other submissions of the same URL, while an external URL yields the threads that submitted it. That duality is exactly what separates this tool from get_post or search_reddit, and an agent can tell which behavior it will get without opening the 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?

The description gives clear conditional guidance keyed on the input the agent already holds — pass a Reddit post for crossposts, pass an article/repo/video URL for submitting threads — so usage is largely self-selecting. It stops short of naming an alternative or stating when not to use it (e.g. when you want comment content rather than link threads), so it is clear context without exclusions.

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