Skip to main content
Glama
thetomtoro

reddit-leads-mcp

by thetomtoro

search_reddit

Find recent Reddit posts matching a query, optionally restrict to specific subreddits. Get post title, body, URL, and engagement stats to spot buying-intent conversations.

Instructions

Search Reddit for recent posts matching a query, optionally restricted to specific subreddits. Returns post title, body, url, and engagement stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNoRecency window (default: week)
limitNoMax posts to return (default: 25)
queryYesSearch query, e.g. 'lead generation tool'
subredditsNoSubreddit names without the r/ prefix, e.g. ['SaaS', 'startups']
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return payload (title, body, url, engagement stats) and the optional subreddit restriction, but does not mention sorting, pagination, or rate limits. This is adequate but not rich.

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?

The description is two sentences: the first states the primary action and optional restriction, the second states the return fields. No unnecessary words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with comprehensive parameter documentation, the description provides sufficient context: it covers the purpose, optional scope, and return fields. No output schema exists, but stating the returned fields is adequate for agent invocation.

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% with detailed parameter descriptions including defaults, enums, and examples. The description adds no parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states that the tool searches Reddit for recent posts matching a query, optionally restricted to subreddits. This specific verb+resource combination distinguishes it from sibling tools like fetch_thread, which retrieves a specific thread.

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?

The usage context is implied: use this when you need to discover recent Reddit posts. However, no explicit guidance is provided about when to prefer this over alternatives like fetch_thread, and no exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thetomtoro/reddit-leads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server