Snapchat Ads MCP Server

Overview Schema Source Related Servers Discussions Admin

snapchat get targeting options

snapchat_get_targeting_options

Read-onlyIdempotent

Fetch valid Snapchat targeting values (countries, regions, languages, interests, devices) for an ad account before editing campaigns; supports paginated results.

Instructions

Discover native targeting values before editing: countries, regions, languages, genders, interests and devices. Retains pagination; do not invent category IDs.

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>",
      "category": "<category>"
    },
    "name": "snapchat_get_targeting_options"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum entities per page, 1 to 1000.
`cursor`	No	Opaque cursor from the previous response's next_cursor. Omit on the first request.
`category`	Yes	Targeting catalog to read.
`adAccountId`	Yes	Snapchat ad account UUID listed in SNAPCHAT_ADS_ACCOUNT_IDS; never an organization ID.
`countryCode`	No	Two-letter country code, required for regions, metros and postal codes.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original 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.

Changed2 schema fields changedv1.0.1Oct 26, 2026

addedInput schema / properties / adAccountId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

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"
+  }
+]

First observedv1.0.0Oct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds 'Retains pagination', but the cursor/limit parameters already encode that, so incremental value is limited. The 'do not invent category IDs' warning is the one genuinely additive behavioral signal.

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 tight sentences, front-loaded with the purpose and followed by the constraint. Nothing is redundant or padded.

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?

With a rich schema, an output schema and full annotation coverage, the description only needs to convey intent and the ID-provenance rule, which it does. The partial category enumeration is the only gap, but it is corrected by the schema enum.

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 is already documented in the schema, including the countryCode dependency for regions/metros/postal_codes. The description adds no format or constraint detail beyond that; its partial category list is slightly less complete than the schema enum.

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 specific verb and resource: 'Discover native targeting values', with an enumerated list of categories. It is clearly a read of a reference catalog, distinct from the entity-listing siblings, though it omits metros, postal_codes and age_groups that the schema supports, and does not explicitly distinguish itself from snapchat_get_targeting or snapchat_get_targeting_specs.

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?

'before editing' gives a timing cue and 'do not invent category IDs' implies these values are the sanctioned ID source, which is useful. However, there is no explicit comparison to the closely named siblings snapchat_get_targeting and snapchat_get_targeting_specs, so an agent must infer which tool to pick.

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