Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_archive_subreddits_search

Search archived Reddit subreddit directory entries by name prefix, then filter by NSFW status or subscriber counts and sort results to find relevant communities.

Instructions

Search Reddit's archived subreddit directory. Searches Arctic Shift's native subreddit directory by name prefix. Directory metadata is updated infrequently; subscriber counts are archived snapshots and retrieved_on indicates when the source captured the entry. The selectable fields are limited to the verified public directory fields.

Input Schema

NameRequiredDescriptionDefault
sortNoSort direction
limitNoMaximum subreddits, defaults to 25 and clamps to 100
queryYesSubreddit name prefix, with or without r/
over_18NoFilter by archived NSFW status
sort_byNoSort field
max_subscribersNoMaximum archived subscriber count
min_subscribersNoMinimum archived subscriber count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and delivers important context: directory metadata is infrequently updated, subscriber counts are archived snapshots, retrieved_on reflects source capture time, and only verified public directory fields are selectable. It does not mention pagination or rate limits, but it discloses the key staleness caveats an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loads the core purpose, and includes only relevant caveats about data staleness and field limits. No filler or redundant repetition of the schema is present.

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 seven-parameter search tool with full schema coverage, no annotations, and no output schema, the description supplies the essential context: source, search mode, data staleness, and field limitations. It is sufficiently complete to call the tool correctly, though it could note return-size behavior.

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 all seven parameters are already documented in structured data. The description only echoes the name-prefix nature of the query and does not add meaning for sort, limit, over_18, or subscriber filters; baseline 3 is appropriate.

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 states a specific verb and resource ("Search Reddit's archived subreddit directory") and adds the mechanism ("by name prefix" via Arctic Shift's native directory). This distinguishes it from live subreddit siblings like reddit_subreddit_about and reddit_subreddits_posts, though it does not explicitly name alternatives.

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

Usage Guidelines2/5

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

It explains the search mechanism (name-prefix matching) but gives no explicit guidance on when to choose this tool over sibling tools such as live subreddit lookups. No exclusions or prerequisite conditions are stated.

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