Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_portfolio_summary

Read-only

Compare ad account performance side by side for yesterday and the last 7 days—spend, purchases, ROAS, cost per purchase, attention flags, and currency totals—from read-only server-configured files.

Instructions

All your ad accounts side by side (read-only): for each account yesterday and the last 7 days (spend, purchases, ROAS, cost per purchase), what needs attention, and totals per currency. It reads the accounts whose settings files the server's owner listed in SNAP_PORTFOLIO_FILES; the AI app cannot choose files. Only account-level numbers are returned.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the operational constraint: it reads only accounts listed in SNAP_PORTFOLIO_FILES and the app cannot choose files, which prevents wasted attempts to scope the call. It also discloses the aggregation level (account-level only) and per-currency totals, though it says nothing about behavior when a listed file is missing or invalid.

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?

Three dense sentences, front-loaded with what the tool returns, then the scoping constraint, then the granularity limit. No filler or repetition.

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 parameterless aggregate with no output schema, it conveys the shape of the return (per-account metrics for two windows, attention flags, per-currency totals) plus the fixed account set. The only gap is error/failure behavior when configured files are unreadable.

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?

Zero parameters, so there is no schema semantics to compensate for; baseline is 4. The description correctly conveys that no filtering inputs exist and that account selection happens server-side via environment configuration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope ('All your ad accounts side by side'), the metrics returned (spend, purchases, ROAS, cost per purchase), the time windows (yesterday and last 7 days), and the granularity ('Only account-level numbers'). This cleanly separates it from single-account siblings without needing to name them.

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?

Implies usage as a portfolio overview ('what needs attention'), and the read-only + fixed-file-set constraints tell the agent it cannot be redirected. However, it never explicitly says when to call this versus an account-specific or anomaly-check sibling, leaving selection partly to inference.

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