Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

Meta creative fatigue

get_creative_fatigue_metrics
Read-onlyIdempotent

Which Meta creatives are wearing out (frequency up, CTR down): what to replace in the next bulk launch. Detect creative fatigue by analyzing frequency, CTR trend, and CPC over time. Flags fatigue if frequency > 3 and CTR declining > 15%.

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

Input Schema

NameRequiredDescriptionDefault
adset_idNoAd set ID to analyze
campaign_idNoCampaign ID to analyze
date_presetNoDate range (default last_14d)
ad_account_idYesMeta ad account id (act_…), from list_ad_accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, and the description goes further by disclosing the actual detection rule: frequency > 3 combined with CTR declining more than 15%, computed alongside CPC trend. That threshold logic is genuinely useful behavior that annotations cannot convey. What it omits is the shape of the result set (per-creative list versus summary).

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?

Two compact sentences that front-load the business question and then the method, with no filler. There is minor redundancy between 'wearing out', 'creative fatigue', and 'Detect creative fatigue', but nothing that obscures the definition.

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

Completeness3/5

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

The tool is a read-only analysis call with a fully documented schema and no output schema, so most requirements are met by the structured fields. However, no return format is sketched (does it emit a ranked list of creatives with flags, or a single verdict?), and the adset/campaign scoping parameters are never mentioned, leaving a small gap for an agent deciding how to call it.

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%, so all four parameters are already documented, including the enum values and the last_14d default. The description names the analytical dimensions but adds no scope, format, or default information beyond what the schema already carries, so the baseline of 3 applies.

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 gives a specific verb and resource — identify Meta creatives that are fatiguing — plus the downstream action ('what to replace in the next bulk launch'). This is distinguishable from the many listing/performance siblings (get_ad_creatives, get_top_performers) because it focuses on deterioration over time, though no sibling is named explicitly.

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?

It supplies clear usage context ('what to replace in the next bulk launch') and names the analytical inputs that make it the right call (frequency, CTR trend, CPC). It does not state exclusions or point to alternative tools, so it stops short of full routing guidance.

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