Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_audience_health

Read-only

Audit Snapchat ad audiences to detect segments that are untargetable, too small, stale past 90 days, or unused by any active ad squad, helping you fix targeting and list maintenance gaps.

Instructions

Audience problems (read-only): segments that are not targetable, too small (under 1,000 people) or customer lists not updated for 90+ days, plus segments no ACTIVE ad squad uses.

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

Input Schema

NameRequiredDescriptionDefault
min_sizeNo
stale_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's '(read-only)' largely restates that. What it does add is genuinely useful: the exact definition of a 'problem' (untargetable, under 1,000, stale 90+ days, unused by any ACTIVE ad squad), which tells the agent what qualifies as a finding. It says nothing about result volume, ordering, or what a returned segment record contains.

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?

A single dense sentence that front-loads the read-only nature and the resource, then lists the criteria. No filler or repetition. The nested parentheticals make it slightly harder to parse than it needs to be, 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?

This is a simple read-only tool with two optional params and no output schema, so the bar is modest, and the description covers what qualifies as a problem. Gaps remain on what the agent gets back (per-segment findings with reasons? counts?), and on the fact that the two thresholds are caller-tunable. Adequate but not complete.

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 coverage is 0%, so the description must carry parameter meaning. It does explain the semantics of both thresholds ('under 1,000 people' and 'not updated for 90+ days'), which map to min_size and stale_days. However, it presents them as fixed constants rather than adjustable inputs, so an agent may not realize the defaults can be overridden or that stale_days caps at 720.

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?

The description gives a specific resource (audience segments) and a specific output class (problems), then enumerates the three problem categories: untargetable, undersized, and stale customer lists, plus unused-by-active-ad-squad segments. This clearly distinguishes it from sizing/insights siblings such as snap_audience_size or snap_audience_insights. It stops short of naming an alternative explicitly, so it is not a 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?

Usage is implied rather than stated: an agent can infer 'call this to audit audience health,' and the enumerated problem categories effectively define what triggers a finding. There is no explicit when-to-use or when-not-to-use statement, and no routing to a sibling for the non-problem cases (e.g. healthy audience sizing).

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