Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

TikTok / Snapchat account performance

get_platform_overview
Read-onlyIdempotent

Spend, ROAS and CPA of one TikTok or Snapchat ad account, in its own currency. TikTok or Snapchat: one ad account's totals over a date range (spend, impressions, clicks, CTR, CPC, CPM, reach, purchases, revenue, ROAS, CPA, add to cart). 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_account_overview.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoYYYY-MM-DD, with until (both included), instead of date_preset
untilNoYYYY-MM-DD, with since
platformYestiktok or snapchat (Meta has its own reads and actions)
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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: money is returned in the ad account's own currency and days in its time zone, and results are per-platform only. It stops short of noting rate limits, empty-range behavior, or attribution windows.

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 core purpose and metric list are front-loaded, and the alternative-tool pointer is placed last where it belongs. The prose is dense with parenthetical detail and the metric enumeration is long, but every clause carries information rather than 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?

With no output schema, the description compensates by listing the returned fields and flagging currency and time-zone semantics, which is what an agent needs to interpret results. Minor gaps remain around blank/no-data responses and whether historical ranges are bounded by platform retention.

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 100% and the schema itself is rich — date_preset enumerates values and default last_7d semantics, since/until include format and pairing rules, ad_account_id explains its source and per-platform ID shape. The description adds no per-parameter meaning beyond this, so the baseline 3 applies.

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?

The description names a concrete verb set and resource — spend, ROAS and CPA totals for one TikTok or Snapchat ad account over a date range — and explicitly enumerates the returned metrics. It also distinguishes itself from get_account_overview for Meta, so an agent can pick it out of a 50-tool sibling list without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit inclusion criteria (one ad account, one platform, date range) and an explicit exclusion with the alternative named: 'For Meta: get_account_overview.' It further warns never to add TikTok and Snapchat together, which prevents a real aggregation mistake.

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