Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_audience_insights

Read-only

Compare Snapchat targeting audiences with a baseline to see which age groups, genders, languages, interests, and devices over- or under-index. Use read-only insights to pick targeting or see reach.

Instructions

Who is in an audience? (read-only, Snap's Audience Insights) For a targeting you describe (countries, ages, gender, interests), shows which age groups, genders, languages, interests and devices appear MORE or LESS than in the comparison audience (default: everyone in the same countries), with an index (1.5 = 50% more likely). Use it to choose targeting or to understand who your ads reach. Changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snap_audience_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
genderNo
max_ageNo
min_ageNo
os_typeNo
categoryNoOnly one kind of insight: demo, geo, device, interest, engagement, aggregated
countriesNoDefaults to SNAP_DEFAULT_COUNTRY
interestsNoInterest ids such as SLC_11 (see snap_targeting_options)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: the default comparison audience ('everyone in the same countries') and how to read the output ('index 1.5 = 50% more likely', MORE or LESS than the baseline). 'Read-only' and 'Changes nothing' restate the annotation and earn no extra credit, and there is no mention of limits on countries/interests beyond the schema.

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?

The core purpose and read-only guarantee are front-loaded in the first clause, and the parenthetical index explanation is efficiently compact. The closing sentence 'Changes nothing' is largely redundant with 'read-only' at the start and could be cut without losing meaning.

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 read-only, open-world analytics tool with seven optional parameters and no output schema, the description covers what the response conceptually contains (relative index per dimension) and what the comparison baseline defaults to. It is slightly incomplete on how the category filter narrows the result and on os_type, but the agent has enough to invoke it correctly.

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?

With only 43% schema description coverage, the description must carry more weight, and it does map most of the targeting inputs (countries, ages, gender, interests) into a coherent picture of what they define. However, it never mentions the os_type parameter or explains that category restricts the response to a single insight kind, so two parameters remain documented only thinly in the schema.

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

Purpose5/5

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

The description opens with a specific question ('Who is in an audience?') and then names the exact output: comparative index scores for age groups, genders, languages, interests and devices against a comparison audience. This clearly separates it from size- or health-oriented siblings such as snap_audience_size and snap_audience_health, which an agent can infer without opening either schema.

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

Usage Guidelines4/5

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

It gives explicit use cases: 'Use it to choose targeting or to understand who your ads reach,' which tells the agent this is a pre-targeting research or post-hoc composition tool. It stops short of naming an alternative sibling or stating when-not to use it (e.g. versus snap_audience_size for reach estimation), which keeps it below a 5.

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