Skip to main content
Glama
Sign In
RedditAPIs

RedditAPIs

by redditapis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_monitor_webhook_delete

Destructive

Permanently delete a Reddit monitor webhook by ID. Monitors using it will fail to deliver until repointed; this action cannot be undone.

Instructions

Permanently delete a webhook. Any monitor still pointing at it will fail to deliver until repointed at a different webhook -- this does NOT cascade-delete or pause the monitors using it. Cannot be undone. Returns 404 webhook_not_found if the id does not exist or is not yours.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe webhook's id, from reddit_monitor_webhook_create's response or reddit_monitor_webhook_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.3

TDQS

A4/5.0
Behavior5/5

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

Despite destructiveHint=true already covering the safety profile, the description adds substantial context: the deletion is permanent and irreversible, it does NOT cascade to monitors (which will fail to deliver until repointed), and it returns 404 webhook_not_found for nonexistent or foreign ids. This is exactly the non-obvious behavior 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.

Conciseness5/5

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

Three tight sentences, front-loaded with the action, then the side-effect warning, then the error condition. Every sentence carries unique information with no redundancy.

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 single-parameter destructive tool with no output schema, the description covers the mutation's permanence, its non-cascading effect on dependent monitors, and the failure mode. Nothing essential for correct invocation 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% and the schema already documents the id's origin, so baseline is 3; the description adds value by disclosing the 404-not-found condition when the id does not exist or is not owned by the caller, which is meaningful semantic detail about the id parameter.

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 opens with a specific verb+resource ("Permanently delete a webhook"), making the operation unmistakable. It does not explicitly contrast with the close siblings reddit_monitor_webhook_create/list/test, so it falls just short of full sibling differentiation.

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 operational consequences of deleting but gives no when-to-use guidance, no prerequisites, and no explicit routing to alternatives such as repointing a monitor or using the webhook test/list tools. The agent must infer usage from context alone.

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