Skip to main content
Glama

Visibility Genies

Read Meta Ads performance

get_meta_ads_performance
Read-only

The connected Meta ad account's Facebook and Instagram ads for a date range, from what the daily pull stored: totals (spend, impressions, link clicks, CTR, CPC, CPM, purchases, leads, registrations, adds to cart and their value, ROAS), each campaign most spend first, and the landing pages the ads send people to. Reach shows for the last 30 or 90 stored days only, as Meta counts people per period. Money is in the account's currency (currencyCode). Results count within 7 days of a click or 1 day of a view. At most 90 days. Read-only; uses no credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_meta_ads_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNoLast day (YYYY-MM-DD). Use with startDate. Without both, the last 30 stored days. At most 90 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day (YYYY-MM-DD, the ad account's time zone). Use with endDate.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
reasonNo
totalsNo
endDateNo
messageNo
failedAtNo
campaignsNo
startDateNo
connectUrlNo
accountNameNo
attributionNo
currencyCodeNo
landingPagesNo
storedThroughNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only' and 'uses no credits' add little. The genuinely additive context is that data comes from a daily pull rather than live Meta, the attribution windows (7-day click / 1-day view), account-currency money, and the reach limitation to 30/90 stored days. Those are useful, but staleness/freshness of the daily pull and pagination or result-size behavior remain unstated.

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?

It is a single dense sentence front-loaded with the resource, followed by short constraint clauses, with no filler or marketing language. The long metric enumeration (purchases, leads, registrations, adds to cart and their value, ROAS) is somewhat wasteful given an output schema exists, which is the main deduction.

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 three fully documented parameters, an output schema, and annotations covering the safety profile, the description only needs to add the non-obvious constraints, which it does: attribution windows, currency, the 30/90-day reach restriction, and the stored-daily-pull origin. The remaining gap is how much data is returned and whether it is paginated or aggregated, but that is minor for a read tool with an output schema.

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 three parameters, including the 30-day default and 90-day maximum, are already documented in the schema. The description largely restates those limits and adds only the account-time-zone nuance, which is also in the startDate schema text. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names the exact platform surface (the connected Meta ad account's Facebook and Instagram ads) and enumerates the returned shapes: totals, per-campaign rows, and landing pages. That makes it separable from get_google_ads_performance, get_tiktok_ads_performance and get_chatgpt_ads_performance without opening any schema. It is phrased as a noun list rather than an explicit 'returns X for Y' verb, which costs it the top mark.

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

Usage Guidelines3/5

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

Usage is implied by platform (Meta vs the other ad-network siblings) and the description states the date-range default and the 90-day cap, so an agent can call it correctly. However, it never says when to prefer this over a sibling or what prerequisite state is needed (e.g., an ad account already connected and pulled), leaving the selection reasoning to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources