Skip to main content
Glama

meta_ads_analysis_placements

Analyze Meta Ads placements to identify underperforming placements causing CPA spikes. Scores delivery efficiency and recommends exclude, keep, or scale actions for each placement.

Instructions

Scores delivery efficiency across Meta placements (Facebook Feed, Instagram Feed, Stories, Reels, Audience Network, Messenger, etc.) and flags the best and worst. Returns rows per placement with spend, conversions, CPA, ctr, and a recommendation (exclude / keep / scale). Read-only. Call this when CPA drifts on a campaign to find whether a single placement is dragging the average. For raw numbers use meta_ads_insights_breakdown with breakdown='placement'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
campaign_idYesCampaign to analyse.
periodNoAnalysis window. Accepts Meta predefined ranges ('today', 'yesterday', 'last_7d', 'last_14d', 'last_30d' (default), 'last_90d') or explicit 'YYYY-MM-DD..YYYY-MM-DD'. Longer windows cost more Graph API quota.
Behavior4/5

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

Declares read-only and describes return rows with specific fields (spend, conversions, CPA, ctr, recommendation). No annotations are provided, so the description carries the full burden, and it does so adequately, though it could mention if any side effects exist (none expected).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences deliver the core purpose and usage context, followed by a one-sentence usage guideline. No wasted words; front-loaded with actionable information.

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

Completeness5/5

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

Given the absence of output schema, the description explains return rows and fields. Schema covers all parameters. Sibling tool references are provided. The description is complete for a placement analysis tool.

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?

Input schema has 100% coverage; all parameters are described in the schema. The description only restates the period options ('Meta predefined ranges ... or explicit'), adding no new meaning. Baseline score of 3 is appropriate.

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?

Description clearly states the tool scores delivery efficiency across Meta placements and flags best/worst. It lists specific placement examples and metrics returned, distinguishing it from sibling meta_ads_insights_breakdown which provides raw numbers.

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?

Explicitly says 'Call this when CPA drifts on a campaign' and directs users to an alternative tool for raw numbers: 'For raw numbers use meta_ads_insights_breakdown with breakdown='placement'.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server