Skip to main content
Glama
Reddit Ads MCP server

Reddit Ads MCP server

by get-mcp-ads

reddit get targeting options

reddit_get_targeting_options
Read-onlyIdempotent

Fetch valid Reddit Ads targeting values for geolocations, languages, interests, devices, carriers, and communities, with pagination and community search to build accurate campaign targeting.

Instructions

Discover valid native targeting values. Communities can be searched; large lists are paginated or explicitly marked partial.

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>",
      "kind": "<kind>"
    },
    "name": "reddit_get_targeting_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesTargeting dimension whose valid values to list.
limitNoItems per page, 1 to 100. Defaults to 50.
queryNoSearch text for communities. Ignored for the other kinds.
cursorNoOpaque next_cursor returned by the previous page. Omit it for the first page.
countryNoTwo-letter uppercase country code, such as US, for kinds that accept a country.
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

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: large result sets are paginated and may be explicitly marked partial, which is important for an agent interpreting completeness of results and is not in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two short sentences with no filler, and the core purpose leads before the pagination caveat. It is arguably over-compressed given the tool's breadth, but 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?

An output schema exists so return shape needn't be explained, and parameter documentation is complete in the schema. However, for a six-parameter enumeration tool spanning six targeting kinds with a near-identical sibling, the description does not say enough about scope or selection to be fully self-sufficient.

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%, so every parameter (kind enum, limit, query, cursor, country, adAccountId) is already documented in the schema, and the description only echoes the community search case. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it discovers 'valid native targeting values', which conveys that this is a reference/enumeration lookup rather than an entity read, but it never states the scope (geolocations, languages, interests, devices, carriers, communities) even though that is the core of the tool. It also fails to distinguish itself from the sibling reddit_get_targeting, leaving the agent to infer the difference.

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?

The only guidance is 'Communities can be searched', which implies the query parameter's applicability but does not say when to call this tool versus reddit_get_targeting or the audience/catalog tools. There are no exclusions or routing conditions, so the agent must guess from the name alone.

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