Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_report_audience

Read-only

Retrieves read-only performance metrics split by country, gender, age, region, DMA, or make for a Snapchat campaign, ad squad, or ad.

Instructions

Performance split by country, gender, age, region, dma or make (read-only), for a campaign, ad squad or ad.

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": {
      "entity": "<entity>",
      "id": "<id>",
      "dimension": "<dimension>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "snap_report_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
end_timeYes
dimensionYes
start_timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

C2.7/5.0
Behavior2/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)' merely restates the annotation rather than adding context. It says nothing about what metrics are returned, whether rows can be empty for sparse dimensions, rate limits, or time-range constraints — the behavioral burden falls on annotations that only cover the safety profile.

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 front-loaded sentence with no filler; the dimension enumeration is the payload and arrives immediately. Slightly dense with the parenthetical and the 'or' chain, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter reporting tool with no output schema, so the description carries the burden of explaining what comes back and how to form a valid request. It delivers neither, leaving time format, id/entity pairing, and return shape entirely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all five parameters rely on the description, which only echoes the two enum value sets already present in the schema. The critical semantics are missing: the expected format/timezone of start_time and end_time, and what the `id` must reference relative to the chosen `entity`.

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 resource (performance breakdown) plus the exact dimension set (country, gender, age, region, dma, make) and the entity levels it can be scoped to (campaign, ad squad, ad). An agent can tell this is a demographic/geo breakdown report. It does not distinguish itself from siblings like snap_report or snap_report_daily, so it stops short of 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 Guidelines2/5

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

There is no explicit when-to-use statement and no named alternative. The dimension list implies 'use this when you need demographic/geo splits rather than a standard report,' but that inference is left entirely to the agent, and no exclusions or prerequisites are given.

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