Skip to main content
Glama
Sign In
RedditAPIs

RedditAPIs

by redditapis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_subreddit_moderators

Read-only

Get a subreddit's moderator team by name. See who moderates a community, including permissions, flair, and join date.

Instructions

Fetch a subreddit's moderator team by name (Reddit's /r//about/moderators data). Returns a moderators list, each with name, id, mod_permissions, flair_text, and added (when they joined the mod team). Use it to see who moderates a community. Example: name='python'.

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": {
      "name": "<name>"
    },
    "name": "reddit_subreddit_moderators"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSubreddit name WITHOUT the r/ prefix (e.g. 'python'). Required (path parameter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.12

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context by naming the underlying endpoint (/about/moderators) and detailing the return fields (name, id, mod_permissions, etc.), including the meaning of 'added'.

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 compact: two sentences and an example. It front-loads the main purpose and each sentence adds value — endpoint, return structure, usage, and example. No wasted words.

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 read-only tool with one parameter, the description covers the purpose, usage context, return format, and parameter example. The schema and annotations fill in the remaining safety and parameter details, making it complete.

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 input schema already fully describes the 'name' parameter (required, no r/ prefix, path parameter). The description's example 'name='python'' reinforces the format but does not add new semantic information beyond the 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 clearly states the action ('Fetch a subreddit's moderator team') and the specific resource (subreddit by name). It explicitly distinguishes this tool from siblings like reddit_subreddit_about or reddit_subreddit_rules by focusing on moderator team data.

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

Usage Guidelines4/5

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

Provides a clear use case: 'Use it to see who moderates a community.' However, it does not explicitly mention alternatives or when not to use it, which would have made the guidance more complete.

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