Skip to main content
Glama
Sign In
MCP Reddit Server

MCP Reddit Server

by Aanerud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

reddit_top

Get top posts from any subreddit by selecting time period and limit. Specify subreddit to see ranked content for hour, day, week, month, year, or all time.

Instructions

Get top posts from a subreddit by time.

Args: subreddit: Subreddit name (without r/) time_period: hour/day/week/month/year/all limit: Posts to fetch (default: 10)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subreddit": "<subreddit>"
    },
    "name": "reddit_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
subredditYes
time_periodNoweek

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. 'Get' clearly signals a read-only fetch, and the args define the scoping behavior. It does not disclose pagination or rate limits, but for a simple read operation the core behavior is transparent.

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?

One purposeful sentence of intent followed by a compact Args block. Every line earns its place; no filler or repetition of schema titles.

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 three-parameter read tool with an output schema present, the description covers the operation, all parameters, value formats, and defaults. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully documents all three parameters: it explains that subreddit excludes 'r/', enumerates the valid time_period values, and gives limit's default. This adds meaning well beyond the bare schema.

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 opens with a specific verb and resource ('Get top posts from a subreddit') and adds the sorting mode ('top') and time-filter dimension, making it easy to distinguish from sibling tools like reddit_hot or reddit_new.

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 purpose implies the tool is for fetching top-scoring posts in a time window, but it never explicitly states when to use this tool over siblings such as reddit_hot, reddit_new, or reddit_rising, nor does it mention exclusions or prerequisites beyond the subreddit argument.

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