Skip to main content
Glama
redditapis

RedditAPIs

by redditapis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_monitor_deliveries

Read-only

See exactly which Reddit posts your monitor's webhook delivered or attempted, newest first, to answer 'what did I actually get sent'.

Instructions

Delivery history: the actual Reddit posts a monitor's webhook has received (or attempted), newest first, including the real post content (title, subreddit, permalink, author). Answers 'what did I actually get sent', not just 'how many' (see reddit_monitor_health for counts). Every delivered item also carries payload.items[].enrichment: a relevance.score (0-1, how much of THIS monitor's own keyword criteria the item matched -- not a model's confidence), a sentiment (polarity -1 to 1 plus a positive/negative/mixed/neutral label), and an intent.tag (question, recommendation_request, complaint, promotion, praise, or discussion). All three are deterministic keyword/lexicon/rule heuristics computed at no extra cost -- each carries its own method field and NONE of them is a machine-learning or LLM call, so do not describe a score here as ML-derived. Omit id to aggregate history across every monitor you own.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNarrow to one monitor's history. Omit to aggregate across every monitor you own.
limitNoMax rows to return, 1 to 200. Default 50.
beforeNoISO 8601 timestamp cursor for pagination -- pass the `created_at` of the oldest row from the previous page to fetch older deliveries.
statusNoFilter to one delivery status. 'dead' = retries exhausted, gave up. 'suppressed' = matched but deliberately not sent, and `payload.suppressed.reason` says which of the two reasons applied: 'delivery_ceiling' (the monitor's daily cap) or 'stale_item' (the item was already older than the freshness window when we first saw it, so it was withheld rather than delivered as if it were new). A 'stale_item' row is NOT a fault and was NOT rejected by any plan limit, and retrying cannot recover it; `payload.suppressed` carries the age and the threshold. Omit for all statuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the read-only/open-world safety profile, and the description adds substantial behavior beyond that: the semantics of 'dead' vs 'suppressed' (with both suppressed reasons and the note that stale_item is not a fault and cannot be recovered by retry), the deterministic non-ML nature of the enrichment fields, and the pagination contract. This is real disclosure the annotations 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.

Conciseness4/5

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

Front-loads the core definition and keeps every sentence informational, but the enrichment paragraph is dense and slightly redundant ('not a model's confidence' and 'NONE of them is a machine-learning or LLM call' restate the same point). Efficient for the amount of information conveyed, though not maximally tight.

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?

There is no output schema, so the description carries the full burden of describing return values, and it does so by documenting the payload.items[].enrichment shape (relevance.score, sentiment.polarity/label, intent.tag) alongside pagination and status semantics. Nothing an agent needs to call and interpret this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: it re-emphasizes the id-omission aggregation rule and expands thestatus semantics (retrying cannot recover a stale_item, no plan limit was involved) beyond what the schema states. The enrichment detail is output-oriented rather than parameter-oriented, so it does not push this higher.

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?

States a specific resource and scope ('the actual Reddit posts a monitor's webhook has received (or attempted), newest first') and explicitly distinguishes its output from 'how many', naming reddit_monitor_health as the counts-oriented sibling. An agent can route between the two without reading any schema.

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?

Gives explicit when-to-use framing ('what did I actually get sent' vs. counts) and names the alternative tool by name, plus states the aggregation behavior when id is omitted. The conditions that select this tool over its sibling are spelled out rather than inferred.

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