Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_report_compare

Read-only

Compare two time windows for a campaign, ad squad, or ad to review changes in spend, purchases, ROAS, CPA, frequency, and swipe rate, with optional child breakdown. Read-only.

Instructions

Compare two time windows for a campaign, ad squad or ad, optionally per child (ad squads or ads): spend, purchases, ROAS, CPA, frequency, swipe rate and the changes (read-only).

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>",
      "current_start": "<current_start>",
      "current_end": "<current_end>",
      "previous_start": "<previous_start>",
      "previous_end": "<previous_end>"
    },
    "name": "snap_report_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
breakdownNo
current_endYes
previous_endYes
current_startYes
previous_startYes

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 and openWorldHint, so the 'read-only' parenthetical adds nothing. The metric list (spend, purchases, ROAS, CPA, frequency, swipe rate and changes) does add useful context about what the comparison returns, but nothing is said about date handling, ordering, or result size.

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 that names the operation, scope and metric set with no filler. The metric enumeration is dense but each item earns its place given there is no output schema.

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?

With no output schema the metric list is a valuable addition, and the entity/breakdown relationship is explained. However, a comparison tool with six required parameters and no date format guidance leaves a meaningful gap an agent could trip over.

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 0% across 7 parameters, so the description must carry meaning and it only partly does. It clarifies that entity accepts campaign/adsquad/ad and that breakdown is the optional per-child dimension, but leaves the four date parameters' format and the id's expected value undocumented.

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 states a specific verb and resource: compare two time windows for a campaign, ad squad or ad, with an optional breakdown per child. That is clear and distinct from a plain reporting tool like snap_report, though it does not name a sibling to contrast against.

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 by the statement of comparing two time windows and the optional per-child breakdown, but there is no explicit when-to-use or when-not guidance versus snap_report, snap_report_daily or snap_creative_compare.

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