Skip to main content
Glama
thenavidm

reddit-research-agent

by thenavidm

Browse a subreddit

browse_subreddit
Read-only

Retrieve posts from a subreddit sorted by hot, new, top, rising, or controversial to support Reddit research and analysis.

Instructions

List posts from one subreddit by hot, new, top, rising, or controversial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum posts to return.
listingNoWhich listing to read.hot
subredditYesCommunity name, with or without the r/ prefix.
timeFilterNoFor top and controversial only.week
Install Server

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark the tool as readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the scoping detail that it lists posts from a single subreddit, but it does not discuss pagination, return format, or error behavior.

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 a single, clear sentence with no filler. It front-loads the action and resource, and it does not duplicate schema details unnecessarily.

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?

For a simple, read-only list tool with full schema coverage and supportive annotations, the description plus schema is largely sufficient to invoke the tool correctly. A minor gap is the lack of any mention of the returned post shape or pagination, but no output schema exists and the tool's behavior is straightforward.

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 each parameter already explained in the input schema. The description mostly restates the listing enum and adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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?

The description clearly states the verb 'list' and the resource 'posts from one subreddit', with the available listing types enumerated. It is distinguishable from siblings like search_reddit and get_thread, though it does not explicitly name them.

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 phrase 'from one subreddit' implies the tool's scope and suggests it is not for cross-subreddit search or single-thread retrieval. However, there is no explicit when-to-use guidance or mention of alternatives such as search_reddit or get_subreddit_info.

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

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/thenavidm/reddit-research-agent'

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