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

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create saved audience

reddit_ads_create_saved_audience

Create a saved audience to store targeting configurations and reuse them across ad groups via saved_audience_id.

Instructions

Save a targeting configuration to reuse on ad groups via saved_audience_id.

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

Input Schema

NameRequiredDescriptionDefault
dataYesSent as {"data": {...}}. Fields: name, type: "REDDIT_AUDIENCE", targeting (same as ad group targeting, without locations and platforms).
ad_account_idNoAd account ID (t2_... or a2_...). Defaults to REDDIT_ADS_ACCOUNT_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds meaningful context — that the saved audience is reusable on ad groups via saved_audience_id — but says nothing about required scopes, whether duplicates are rejected, or idempotency.

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?

A single front-loaded sentence with no filler. The purpose and the reuse mechanism are stated immediately, and nothing is wasted.

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

Completeness4/5

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

For a 2-param create tool with a fully documented schema and annotations covering the safety profile, the description is nearly sufficient; naming saved_audience_id effectively communicates the handle returned. It could mention auth/account-scope requirements, but nothing critical for invocation is missing.

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 coverage is 100%, so the schema already documents both the nested data fields and ad_account_id default. The description mentions 'targeting configuration' generically but adds no syntax, format, or constraint detail beyond what the schema provides; baseline 3 applies.

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+resource ('Save a targeting configuration') and explains the reuse purpose via saved_audience_id. It implicitly distinguishes itself from list_/get_/update_saved_audience siblings by being the creation step, but never names an alternative explicitly.

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 when-to-use guidance, no prerequisite (e.g. that an ad account must exist), and no routing versus update_saved_audience or list_saved_audiences. The phrase 'reuse on ad groups' hints at intent but does not tell the agent when this tool is the right choice.

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