Skip to main content
Glama
Reddit Ads MCP server

Reddit Ads MCP server

by get-mcp-ads

reddit get targeting

reddit_get_targeting
Read-onlyIdempotent

Retrieve Reddit ad group targeting configuration, including inclusions, exclusions, geo, age/gender, languages, interests, communities, keywords, devices, and audience IDs.

Instructions

Read actual ad-group targeting: inclusions, exclusions, geo, age/gender, languages, interests, communities, keywords, devices and audience IDs. This is configuration, not delivery demographics.

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": {
      "adAccountId": "<adAccountId>",
      "adGroupId": "<adGroupId>"
    },
    "name": "reddit_get_targeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
adGroupIdYesAd group ID whose targeting to read. It must belong to adAccountId.
adAccountIdYesReddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the meaningful distinction that the payload is configuration rather than delivery demographics, which prevents misreading of the output. It says nothing about scoping, error behavior, or account/ad-group ownership requirements beyond what the schema already carries.

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 short sentences, zero filler. The field inventory is front-loaded and the disambiguating clause comes last, which is exactly the right ordering for an agent skimming definitions.

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?

An output schema exists so return values need not be explained, and the description still names the returned categories, which helps an agent decide whether this call answers its question. Parameters are fully covered by the schema. What is missing is any routing hint to the neighboring targeting/insights tools.

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 description coverage is 100% and both parameters are documented there, including the a2_ prefix convention and the adAccountId/adGroupId ownership constraint. The description adds no parameter-level information beyond the schema, so the baseline of 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?

Specific verb + resource ('Read actual ad-group targeting') followed by an explicit field inventory (inclusions, exclusions, geo, age/gender, languages, interests, communities, keywords, devices, audience IDs). The closing clause distinguishes it from delivery-based reporting tools like reddit_get_insights. It does not directly differentiate from the similarly named sibling reddit_get_targeting_options, which keeps it at 4 rather than 5.

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?

'Read actual ad-group targeting' plus 'This is configuration, not delivery demographics' implies the use case (fetch configured settings, not performance data) and gives one useful exclusion. However, no sibling is named and there is no explicit when-to-use statement contrasting it with reddit_get_targeting_options or reddit_get_ad_group.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.