Skip to main content
Glama

Delimit Reddit Scan

delimit_reddit_scan
Read-onlyIdempotent

Scan 25+ subreddits in bulk to uncover ranked, categorized outreach targets ready for comment drafting.

Instructions

Bulk scan 25+ subreddits for outreach targets (Pro).

When to use: as a venture-agnostic bulk Reddit scan — returns ranked, categorized targets ready for comment drafting. When NOT to use: for venture-scoped scan (use delimit_reddit_fetch_thread or delimit_social_target) or one specific thread.

Sibling contrast: delimit_reddit_fetch_thread is single thread; delimit_social_target is multi-platform venture scan; this is the broad Reddit pass.

Side effects: read-only network via residential proxy. Rate limited to 1 req / 2sec. The orchestrator must chain (per rule below).

IMPORTANT -- TOOL CHAINING RULE: After scanning, the AI MUST process high_priority targets:

  1. Draft replies via delimit_social_post or delimit_notify

  2. Create ledger items for strategic opportunities via delimit_ledger_add Never just return targets and stop. Always chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoReddit sort order — "hot" (default), "new", "top".hot
limitNoPosts per subreddit. Default 10, max 25.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv4.7.9
    • changedInput schema / properties / limit / description
      Previous value: -"Posts per subreddit (default 10, max 25)."New value: +"Posts per subreddit. Default 10, max 25."
    • changedInput schema / properties / sort / description
      Previous value: -"Reddit sort order (hot, new, top)."New value: +"Reddit sort order — \"hot\" (default), \"new\", \"top\"."
  2. Addedv4.5.5

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses read-only network access via residential proxy, a 1 req/2sec rate limit, and a mandatory tool-chaining rule after scanning. This adds substantive behavioral context that annotations alone do not provide.

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 well-structured and front-loaded: the core purpose appears first, followed by usage guidance, side effects, and the chaining rule. Every section earns its place and the text is dense without being bloated.

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?

The tool is fully contextualized for an agent: clear purpose, explicit alternative routing, side-effect disclosures, rate limiting, and a mandatory follow-up chain. With an output schema present and annotations covering safety, nothing essential is missing for correct invocation and follow-through.

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 already fully documents the sort and limit parameters. The description does not add new parameter-level semantics, but this is acceptable because the baseline of 3 applies when the schema carries the load.

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: bulk scanning 25+ subreddits for outreach targets. It further distinguishes itself by stating it is venture-agnostic and returns ranked, categorized targets, which clearly separates it from sibling tools like delimit_social_target and delimit_reddit_fetch_thread.

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 provides explicit 'when to use' and 'when NOT to use' guidance, names the alternative tools by name, and includes a sibling contrast section. An agent can confidently route to this tool versus the alternatives without ambiguity.

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/delimit-ai/delimit-mcp-server'

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