Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

TikTok / Snapchat performance per day

get_platform_daily_breakdown
Read-onlyIdempotent

TikTok or Snapchat results day by day. TikTok or Snapchat: day by day over a date range (92 days at most, every day listed, zeros when nothing delivered), for the whole ad account or ONE campaign_id / adset_id / ad_id; with the range's totals. Money in the ad account's currency, days in its time zone; one platform at a time (never add TikTok and Snapchat up). For Meta: get_daily_breakdown.

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": {
      "platform": "<platform>",
      "ad_account_id": "<ad_account_id>"
    },
    "name": "get_platform_daily_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idNoOne ad's days
sinceNoYYYY-MM-DD, with until (both included), instead of date_preset
untilNoYYYY-MM-DD, with since
adset_idNoOne ad group / ad squad's days
platformYestiktok or snapchat (Meta has its own reads and actions)
campaign_idNoOne campaign's days instead of the whole ad account
date_presetNoDefault last_7d (the 7 days before today, today left out), in the ad account's time zone
ad_account_idYesThe ad account, from list_ad_accounts with the same platform: a TikTok advertiser id (digits), a Snapchat ad account id (a UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantive behavior: a hard 92-day cap, zero-filled rows for days with no delivery, range totals included, currency and time zone inherited from the ad account, and strict per-platform isolation. These are the exact constraints an agent would otherwise get wrong by summing platforms or assuming sparse rows.

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?

Dense and information-rich with no filler, but the opening line 'TikTok or Snapchat results day by day' is essentially restated as 'TikTok or Snapchat: day by day over a date range', so the front-loading repeats itself. The 92-day cap and the Meta pointer are well placed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description has to carry the return semantics, and it does: per-day rows including zeros, plus range totals, in account currency and time zone. Combined with the 92-day cap and platform exclusivity, an agent has everything needed to call it correctly and interpret the result.

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 coverage is 100%, so all eight parameters are documented in-schema; baseline is 3. The description does add some meaning the schema lacks, notably that the scope parameters select ONE campaign/adset/ad instead of the whole account and that ad_account_id formats differ per platform (advertiser id vs UUID), but it stays at the level the schema already conveys for date_preset/since/until.

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 read of a specific resource: day-by-day results for TikTok or Snapchat over a date range, at account/campaign/adset/ad level. It explicitly contrasts with the Meta counterpart (get_daily_breakdown) and with per-platform scope, so an agent can separate it from get_platform_performance or get_platform_overview without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating conditions: one platform at a time, never sum TikTok and Snapchat, max 92 days, and route to get_daily_breakdown for Meta. It does not explicitly say when to prefer get_platform_performance or get_platform_overview over this daily-grain tool, so the sibling routing is only partially complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources