Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

List ads (Meta, TikTok, Snapchat)

list_ads
Read-onlyIdempotent

The ads of any connected Meta, TikTok or Snapchat ad account (ids and names, no metrics). List the ads of an ad account, optionally of one campaign or ad set (e.g. to pick the ad whose page, texts, URL and CTA are copied).

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": "list_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNo
adset_idNo
platformNoAd platform, default meta
campaign_idNo
ad_account_idYesAd account id (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?

Beyond the read-only and idempotent annotations, the description adds useful output context by stating that results contain ids and names and no metrics. It still omits pagination behavior and any auth or rate-limit notes, but with safety already covered by annotations, the added return-scope detail is meaningful.

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 description is only two sentences and front-loads the main purpose and scope, with no wasted exposition. The first sentence is a fragment and the creative-field example is slightly ambiguous, but overall it is compact and easy to scan.

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?

For a five-parameter read-only list tool with no output schema, the description covers the core purpose, optional filters, and minimal return content. It leaves important gaps around the search parameter, pagination, and how this differs from get_ads, so it is adequate but not fully complete.

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 40%, and the description explains the optional campaign/ad set filtering and platform scope. However, it does not explain the search parameter at all, so it only partially compensates for the low schema coverage.

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 ('List the ads') and scopes it to connected Meta, TikTok, or Snapchat ad accounts, optionally by campaign or ad set. It also states that results are ids and names with no metrics, which helps distinguish it from performance-oriented siblings, but it does not explicitly name alternatives such as get_ads.

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 provides a clear use case: listing ads to pick one whose page, texts, URL, and CTA are copied. It does not explicitly say when to use this instead of get_ads or other ad-related siblings, and there are no exclusions, so routing guidance is present but incomplete.

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