Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_report_hourly

Read-only

Breaks down spending, purchases, ROAS, and cost per purchase by local hour of day for up to 7 days, highlighting your best and worst hours and four dayparts at account, campaign, ad squad, or ad level.

Instructions

Which hours of the day work best? (read-only) Spend, purchases, ROAS and cost per purchase for each local hour of the day, summed over the last 1-7 full days, with the best and worst hours and four dayparts. Account level by default, or one campaign, ad squad or ad. Hours follow SNAP_REPORT_UTC_OFFSET.

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

Input Schema

NameRequiredDescriptionDefault
idNoRequired unless entity is adaccount
daysNo
entityNoadaccount

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to re-litigate safety. It adds genuine behavioral context beyond the annotations: aggregation is over the last 1-7 FULL days, results include best and worst hours and four dayparts, and hours are governed by the SNAP_REPORT_UTC_OFFSET setting — a non-obvious timezone dependency for hourly data.

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?

The content is dense and front-loaded: purpose question first, then metrics, then scope, then the timezone caveat, all in one compact paragraph with no filler sentences. The rhetorical opening question costs a few words but efficiently frames the use case.

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?

With no output schema, the description does the job of explaining what comes back — the per-hour metrics, best/worst hours, and daypart rollups — which is enough for an agent to decide whether the shape fits. The only modest gap is the absence of explicit guidance on pagination or limits, which is minor for a fixed 24-hour breakdown.

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

Parameters4/5

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

Schema description coverage is only 33%, so the description carries real weight here: it clarifies that entity selects account vs campaign/adsquad/ad granularity, that account level is the default, and that the id parameter is the entity identifier (implicitly required when not at account level). It also bounds 'days' to the 1-7 full-day window, adding meaning beyond the bare integer schema.

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 resource and dimension: spend, purchases, ROAS and cost-per-purchase broken out per local hour, plus best/worst hours and four dayparts. That is concrete enough to distinguish it from generic reporting siblings, but it never names a specific alternative (e.g. snap_report_daily) so the differentiation is left implicit.

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?

"Account level by default, or one campaign, ad squad or ad" gives clear scoping context and the 1-7 full-day window bounds the analysis period. However, there is no explicit when-to-use/when-not-to-use guidance or a pointer to the daily/compare siblings for other breakdowns, so usage is only implied.

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