Skip to main content
Glama

reddit_subreddits_new

Read-only

Discover recently created subreddits without a keyword. Returns each subreddit's name, title, subscriber count, description, type, NSFW flag, and pagination cursor.

Instructions

Browse the newest subreddits, the communities most recently created, no keyword needed. Returns a subreddits list (each with name, title, subscriber count, description, type, and NSFW flag) plus an after cursor for paging. This BROWSES communities by recency; use reddit_search_communities instead to SEARCH communities by keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOpaque Reddit pagination cursor from the previous response's `after` field (a fullname like `t3_abc123`). Omit on the first call; pass it to fetch the next page.
limitNoMax items to return (1 to 100). The API clamps out-of-range values; endpoint default applies if omitted.
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return structure (list of subreddits with specific fields) and pagination behavior (after cursor). This is more than mere restatement and provides useful behavioral context.

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 three sentences, front-loaded with the core purpose, followed by output details and a clear alternative tool reference. Every sentence contributes meaningful information with no redundancy or filler.

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?

Given the simple 2-parameter schema and no output schema, the description fully covers what an agent needs: it explains the return fields, the pagination cursor, and the difference from a sibling tool. This is sufficient for a read-only listing operation.

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?

The schema covers 100% of parameters with detailed descriptions for 'after' and 'limit'. The tool description mentions the 'after' cursor but does not add further meaning beyond the schema. With full schema coverage, a baseline of 3 is appropriate; the description does not contribute extra semantic value.

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 identifies the action ('Browse the newest subreddits') and the specific resource, distinguishing it from sibling tools by framing it as recency-based browsing. It explicitly contrasts with reddit_search_communities, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states when to use this tool ('newest subreddits, no keyword needed') and explicitly names the alternative for keyword-based searches: 'use reddit_search_communities instead to SEARCH communities by keyword.' This provides clear when/when-not guidance.

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/redditapis/redditapis-mcp'

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