Skip to main content
Glama
mariocodesforfun

Meta Ads Codex MCP

meta_ads_performance_trend

Analyze Meta Ads performance trends by providing ad account and entity IDs, then selecting a metric like ROAS, CPC, or CPM to see changes over time.

Instructions

Read-only. Ask Meta's insight tool for performance trend analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idsNo
ad_account_idNo
analysis_levelNo
analysis_metricNo
advertiser_requestNo
conversation_topicNo
conversation_intentNo
Behavior2/5

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

The description discloses 'Read-only,' which is a useful safety trait given there are no annotations. However, it provides no other behavioral context, such as return format, data granularity, rate limits, or what 'trend analysis' entails. With annotations absent, this is insufficient disclosure.

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

Conciseness2/5

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

The description is extremely short, but this is under-specification rather than conciseness. While it is front-loaded with the read-only note, the core phrase 'performance trend analysis' adds little beyond the tool name and fails to provide meaningful structure or context.

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

Completeness1/5

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

With 7 undocumented parameters, no output schema, no annotations, and a one-sentence description, the tool is severely incomplete. Nothing explains how to construct a request, what results look like, or how this fits with the broader Meta Ads tool family.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 7 parameters with 0% description coverage, and the tool description does not explain any of them. Entity IDs, ad_account_id, metrics, and other fields are left entirely undefined, so an agent has no idea what values to supply or what they control.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool is for 'performance trend analysis,' which is a clear function but remains vague about the specific output or scope. It does not distinguish this from sibling tools like meta_ads_ad_performance, which likely also deals with performance metrics. The purpose is acceptable but lacks specificity.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of alternatives like meta_ads_ad_performance or meta_ads_account_summary. The description simply says 'Ask Meta's insight tool,' which does not convey any usage context, exclusions, or prerequisites.

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/mariocodesforfun/meta_ads_codex_mcp'

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