Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_get_stats

Read-only

Retrieve read-only performance stats for a campaign, ad squad, or ad across a specified time window to audit impressions, spend, and conversions.

Instructions

Stats for one campaign, ad squad or ad over a window (read-only). Times must fall on the hour; spend is in micro-currency.

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

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
fieldsNo
end_timeYes
start_timeYesISO date-time on the hour, with offset, e.g. 2026-10-19T00:00:00+00:00
granularityNoTOTAL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

B3.2/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 safety is covered. The description adds useful behavioral details—spend is in micro-currency and times must fall on the hour—but does not explain error behavior, granularity effects, or pagination.

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 tightly written sentences with zero waste. The entity scope is front-loaded, followed by the window constraint and the two most important caveats.

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?

For a six-parameter analytics tool with low schema coverage and no output schema, the description is too thin. It omits field selection behavior, granularity semantics, id format, and return shape, leaving the agent to infer key details.

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 only 17%, so the description must compensate. It clarifies entity choices and time alignment, plus spend units, but leaves id, fields, and granularity (TOTAL/DAY/HOUR) unexplained beyond their schema enums.

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 verb ('Stats') and resource ('campaign, ad squad or ad') with a clear window scope. An agent can tell this is a per-entity stats retrieval tool, though it does not name a sibling alternative for comparison.

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 phrase 'over a window (read-only)' implies usage context, and the hour constraint is a practical filter. However, it gives no explicit when-to-use guidance versus siblings like snap_get_entity or snap_api_get, nor any exclusions.

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