Skip to main content
Glama
filippofinke

reddit-ads-mcp

by filippofinke

Delete product feed

reddit_ads_delete_product_feed
Destructive

Permanently deletes a Reddit Ads product feed by feed ID, removing it from your catalog when it is no longer needed.

Instructions

Permanently delete a product feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feed_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is largely covered. The word 'Permanently' adds useful confirmation of irreversibility, but the description does not describe authorization requirements, cascading effects, or what happens to associated product sets or products.

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 a single, front-loaded sentence with no filler or repetition. It is optimally concise, though the terseness contributes to gaps captured in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, one-parameter tool with no output schema, the description is too sparse. It omits how to obtain the feed_id, permission requirements, and whether deletion cascades to related entities, leaving meaningful gaps despite annotations covering the basic destructive nature.

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

Parameters2/5

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

The schema has 0% description coverage and the description does not explain feed_id at all. While the parameter name is somewhat inferable from the tool's purpose, the description fails to compensate for the missing schema documentation by stating format, source, or constraints.

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: 'Permanently delete a product feed.' This clearly identifies the operation, but it does not distinguish this tool from sibling deletion tools such as reddit_ads_delete_products or reddit_ads_delete_product_set, so the agent must infer scope from the name alone.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action without telling the agent under what conditions deletion is appropriate or which related tools to use instead.

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