Skip to main content
Glama
Sign In
reddit-ads-mcp

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update saved audience

reddit_ads_update_saved_audience

Update a saved audience's name, targeting, or status, or delete it by setting status to DELETED.

Instructions

Update a saved audience. Set status to DELETED to delete it.

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": {
      "saved_audience_id": "<saved_audience_id>",
      "data": "<data>"
    },
    "name": "reddit_ads_update_saved_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesSent as {"data": {...}}. Fields: name, status, targeting.
saved_audience_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The description adds genuinely useful behavioral context by disclosing that the 'delete' path is a status mutation to DELETED, which the annotations do not reveal. destructiveHint=false could be read as inconsistent with 'delete it', but it is reconcilable as a soft/status-based delete; the description doesn't say whether the update is a partial patch or full replace, nor whether permissions are required.

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?

Two sentences, zero filler, purpose front-loaded with the delete path immediately after. Nothing is wasted.

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

Completeness3/5

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

For a 2-param mutation tool with a nested data object, no output schema, and no annotations covering semantics, the description covers the core operation and the deletion shortcut but omits merge/patch semantics, required permissions, and error behavior. Adequate but with identifiable gaps.

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?

Schema coverage is only 50% and there are no enums, so the description carries extra burden. It nicely clarifies the status value ('DELETED') but says nothing about the 'name' or 'targeting' fields, nor about how the nested data object is merged into existing settings.

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?

States a concrete verb+resource ('Update a saved audience') and even names the deletion mechanism, so the agent knows exactly what operation this performs. It doesn't differentiate itself from the get/list/create_saved_audience siblings, but the name and description together make the CRUD position obvious.

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

Usage Guidelines3/5

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

There's no explicit when-to-use or when-not-to-use guidance, but the second sentence does route the agent usefully: deletion of a saved audience is done here via status=DELETED rather than through some other tool. That's implied usage rather than stated policy.

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