Search Reddit posts.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, 1-12 (default: 1). 20 posts per page | |
| query | Yes | Search keyword (max 500 characters) | |
| sort_by | No | Sort order: "most_recent", "relevance", "hot", or "top" | most_recent |
| get_sentiment | No | Add AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small per-page surcharge. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / page / descriptionPrevious value: -"Page number, 1-5 (default: 1)"New value: +"Page number, 1-12 (default: 1). 20 posts per page"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Search Reddit posts.' It does not mention pagination limits, sort behavior, the sentiment analysis option, rate limits, or what fields are returned, so an agent gets minimal insight into the tool's actual behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and free of filler, with the core purpose front-loaded. While it could include more useful context, as a concise statement it is well-structured and immediately scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no annotations and no output schema, so the description should provide more context about what the agent can expect from the result and any important limitations. 'Search Reddit posts' alone is too thin to be considered complete for a search tool with pagination, sorting, and optional sentiment analysis.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and each parameter already has a meaningful description. The tool description adds no extra parameter context, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Search') and a specific resource ('Reddit posts'), which clearly distinguishes it from sibling tools like search_reddit_comments and search_reddit_users. It adds value beyond the tool name by narrowing the resource to posts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool vs. alternatives. It does not mention search_reddit_comments, search_reddit_users, or any exclusions, leaving the agent to infer usage purely from the name and siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly scoped by platform and resource (e.g. search_twitter vs twitter_user_tweets vs twitter_tweet_details). A few pairs like twitter_tweet_comments vs twitter_user_replies or facebook_page_posts vs search_facebook_posts could cause minor confusion, but descriptions generally clarify the distinction.
The dominant pattern is snake_case with a platform_prefix_resource suffix, and search_* consistently marks search operations. Minor deviations include noun-style names like amazon_best_sellers and place_photos, and the odd get_ skill/comments tools, but the overall convention is predictable.
74 tools is far beyond the typical well-scoped MCP server, even for a multi-platform API aggregator. The breadth is justified by the many platforms covered, but an agent will face a very large action space, and this could reasonably be split into per-platform servers.
The server provides strong lifecycle coverage for its read-only domain: search, profile/details, posts, and engagement data across most platforms. Gaps exist for some platforms (e.g. no LinkedIn person profile, no Facebook event details, no Truth Social profile/search, no Reddit subreddit-specific tools), but the core workflows are well covered.