Skip to main content
Glama
Sign In
SubScraper Reddit MCP Server

SubScraper Reddit MCP Server

by subscraper-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_popular

Fetch Reddit’s r/popular feed to identify posts trending across all subreddits now; returns titles, scores, subreddit names, and comment counts.

Instructions

Get the current r/popular feed — posts trending across all of Reddit right now. Returns titles, scores, subreddits, and comment counts.

Input Schema

NameRequiredDescriptionDefault
timeNoTime filter: all | year | month | week | day | hour
afterNoPagination cursor from previous nextPageUrl (e.g. "t3_...")
limitNoNumber of results to return (1–100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior5/5

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

Since there are no annotations, the description carries the full burden. It explicitly states the data structure and content returned, listing 'titles, scores, subreddits, and comment counts,' which is critical behavioral context for an agent.

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 definition is a single, highly efficient sentence that gets straight to the point, avoiding unnecessary phrasing.

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?

Given the clear input schema and defined parameters, the description is complete enough. It adds vital context regarding the nature of the returned data (e.g., scores, comments) which guides the user experience.

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%, so the schema fully documents the parameters. The description adds no specific meaning or constraints beyond the structured data provided.

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 identifies the resource (r/popular feed) and the function (trending posts), making the purpose clear. It is distinct from other retrieval tools by specifying 'current' trending status.

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?

Usage is implied: when a user wants to see general trending posts. However, it does not explicitly state when to use it versus more specific sibling tools like `get_leaderboard` or `explore`.

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