Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

Meta campaign performance

get_campaigns

Read-onlyIdempotent

Meta campaigns with their spend and results: what runs and what performs. Get list of campaigns with their performance metrics. Use to see which campaigns are active, their budget, spend, and results.

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

Input Schema

Name	Required	Description
`limit`	No	Max number of campaigns to return (default 25)
`date_preset`	Yes	Date preset for metrics
`ad_account_id`	Yes	Meta ad account id (act_…), from list_ad_accounts
`status_filter`	No	Filter by campaign status

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world query. The description adds some useful context by saying the results include spend and performance metrics, but it does not explain pagination behavior or the shape of the returned campaign performance data beyond a high-level 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?

The description is short and front-loaded, leading with the resource and its performance-oriented purpose. There is minor redundancy between “spend and results” in the first sentence and “budget, spend, and results” later, but it remains efficient.

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 four-parameter read-only listing tool with full schema coverage and annotations, the description provides enough context to understand the resource and its main metrics. The main remaining gaps are return-value structure and explicit sibling differentiation, which are minor for invocation.

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 four parameters are already documented in the input schema. The description reinforces that the tool returns performance metrics and can be used to inspect active campaigns, but it does not add parameter-specific detail beyond what the schema states.

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 clearly states it returns a list of Meta campaigns with performance metrics, including spend, budget, and results. It implicitly distinguishes itself from a basic campaign list by focusing on performance, but it never names the sibling list_campaigns or another alternative.

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 gives a clear usage context: use it to see which campaigns are active and how they perform across budget, spend, and results. It does not state when not to use it or explicitly compare it with list_campaigns or campaign optimization tools.

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 tools Inspect

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.