Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_audience_size

Read-only

Estimates Snapchat audience reach before spending from an ad squad or planned targeting (countries, ages, gender, interests, OS, segments) and flags size as very small, small, OK, or very broad.

Instructions

Snap's estimate of how many people a targeting can reach, BEFORE spending (read-only, nothing is created). Give adsquad_id for an existing ad squad, or the targeting (countries, ages, gender, interests, os, segments) for one you are planning. Says whether the audience is very small, small, OK or very broad.

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_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
genderNo
max_ageNo
min_ageNo
os_typeNo
countriesNo2-letter codes, e.g. ["sa", "ae"]. Defaults to SNAP_DEFAULT_COUNTRY.
interestsNoInterest ids such as SLC_11 (see snap_targeting_options)
adsquad_idNo
exclude_segment_idsNo
include_segment_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description's 'read-only, nothing is created' reinforces rather than contradicts them. It adds genuine context beyond annotations by characterizing the return as an estimate bucket (very small / small / OK / very broad) and noting it is an estimate, which sets expectations about precision.

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?

Three tight sentences, each earning its place: purpose first, then the two input modes, then the output shape. No boilerplate or repetition.

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 9-parameter estimation tool with no output schema, the description covers purpose, both invocation modes, and the qualitative return. Remaining gaps are the precedence rule between adsquad_id and inline targeting and the meaning of include/exclude segment lists, which an agent would need to call it unambiguously.

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 22% schema coverage across 9 parameters, the description compensates partially by grouping the inline targeting fields (countries, ages, gender, interests, os, segments) and identifying adsquad_id as the alternative input path. It never explains exclude_segment_ids vs include_segment_ids, age bounds, or what happens if both adsquad_id and inline targeting are supplied, leaving several parameters undocumented in both schema and description.

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?

States a specific verb and resource ('estimate of how many people a targeting can reach') plus the key scope qualifier 'BEFORE spending'. This clearly separates it from reporting siblings such as snap_report_audience and snap_audience_insights, which measure after delivery.

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?

Gives explicit routing guidance: use adsquad_id for an existing ad squad, or pass targeting fields for a planned one. It also frames the timing ('BEFORE spending'), implying use during planning rather than post-campaign analysis. It does not name a specific alternative tool or state when not to use it, which keeps it below 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