Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_report_daily

Read-only

Retrieve day-by-day performance for a Snapchat campaign, ad squad, or ad—including spend, purchases, ROAS, CPA, and swipe rate—for up to 31 days to audit results.

Instructions

Day-by-day performance (spend, purchases, ROAS, CPA, swipe rate) for a campaign, ad squad or ad, up to 31 days (read-only). Day boundaries must be local midnight with offset.

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>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "snap_report_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
end_timeYes
start_timeYese.g. 2026-10-01T00:00:00+00:00
view_attribution_windowNoPin the view attribution window; default is the account's setting
swipe_up_attribution_windowNoPin the swipe attribution window; default is the account's setting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

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 and openWorldHint=true, so the description's '(read-only)' is redundant. It does add two behavioral constraints beyond the annotations: the hard 31-day cap and the offset requirement for day boundaries, which will cause failures if violated. It stops short of describing response shape, pagination, or how attribution windows affect the reported numbers.

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 sentences, front-loaded with the metric set and scope, followed immediately by the hard limits. Every clause carries information; nothing is padding.

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 6-parameter read-only report with no output schema, listing the returned metrics does much of the work an output schema would. The remaining gap is the shape of the returned rows and behavior at the 31-day boundary, which an agent would have to discover at call time.

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 only 50%, and the description partially compensates by enumerating the entity values (campaign, ad squad, ad) and clarifying that start/end must be local-midnight timestamps with offset, which the schema only shows by example. It says nothing about id, end_time formatting, or how the two attribution-window overrides change results, leaving those to the schema's own text.

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?

Names the resource (campaign, ad squad, or ad) and the exact metrics returned (spend, purchases, ROAS, CPA, swipe rate) at a stated granularity of one day, which distinguishes it from aggregate or hourly report siblings even though none are named. The 'up to 31 days' bound further pins the scope. Not a 5 because no sibling is explicitly contrasted.

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?

The 31-day maximum and the requirement that day boundaries be local midnight with an offset give real usage constraints, implying this is not the tool for long-window or hourly analysis. However, it never routes the agent to alternatives such as an aggregate or hourly report tool, so the when-not-to-use case must be inferred from the sibling list.

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