Skip to main content
Glama
karanb192

Reddit Buddy MCP

by karanb192
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_reddit

Read-only

Search Reddit posts by keyword, subreddit, author, or flair. Sort by relevance, hot, top, new, or comments to find matching content with metadata.

Instructions

Search for posts across Reddit or specific subreddits. Returns matching posts with content and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNorelevance
timeNoall
flairNo
limitNoDefault 25, range (1-100). Override ONLY IF user requests.
queryYesSearch query
authorNo
subredditsNoSubreddits to search in, max 10 (leave empty for all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.1.14
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / author / description
      Removed value: -"Filter by specific username (e.g., \"spez\")"
    • removedInput schema / properties / flair / description
      Removed value: -"Filter by post flair/tag (e.g., \"Discussion\", \"News\")"
    • addedInput schema / properties / limit / default
      Added value: +25
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results (1-100, default: 25)"New value: +"Default 25, range (1-100). Override ONLY IF user requests."
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / query / description
      Previous value: -"Search terms (e.g., \"machine learning\", \"climate change\")"New value: +"Search query"
    • addedInput schema / properties / sort / default
      Added value: +"relevance"
    • removedInput schema / properties / sort / description
      Removed value: -"Result ordering: \"relevance\" (best match), \"hot\", \"top\", \"new\", \"comments\" (most discussed)"
    • changedInput schema / properties / subreddits / description
      Previous value: -"List of subreddits to search in. Leave empty to search all of Reddit (e.g., [\"science\", \"technology\"])"New value: +"Subreddits to search in, max 10 (leave empty for all)"
    • addedInput schema / properties / subreddits / items / description
      Added value: +"Subreddit name without r/ prefix"
    • addedInput schema / properties / subreddits / maxItems
      Added value: +10
    • addedInput schema / properties / time / default
      Added value: +"all"
    • removedInput schema / properties / time / description
      Removed value: -"Time range filter: \"hour\", \"day\", \"week\", \"month\", \"year\", \"all\""
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds that it returns 'content and metadata', which provides some behavioral context but lacks details on rate limits, authentication needs, or pagination behavior. Adequate given annotations.

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?

The description is a single concise sentence with no fluff. It could be slightly expanded to include more guidance on parameter usage without losing conciseness.

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?

Given 7 parameters and no output schema, the description covers the basic purpose but misses operational details like sort/time defaults, limit constraints, and how to use optional filters like flair and author. Adequate for a search tool but has gaps.

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 43% (3 of 7 parameters have descriptions). The description does not add meaning beyond what the schema provides for parameters like sort, time, flair, and author. Baseline 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 the verb 'Search', the resource 'posts', and the scope 'across Reddit or specific subreddits'. It effectively differentiates from sibling tools like browse_subreddit (browsing, not searching) and get_post_details (single post).

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 description implies usage for searching posts but does not explicitly state when to use this tool vs alternatives like browse_subreddit or reddit_explain. No exclusions or when-not scenarios are mentioned.

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