Skip to main content
Glama

meta_ads_analysis_suggest_creative

Analyze recent Meta Ads performance to receive ranked creative-improvement suggestions, such as adding short-form video or rotating headlines, based on data-driven insights.

Instructions

Generates concrete creative-improvement suggestions for a Meta Ads campaign based on recent ad performance. Returns a ranked list of suggestions (e.g. 'add a short-form video — carousel CTR is 2x static image', 'rotate headlines — top-3 CTR ads all use question-form headlines'). Read-only — does not create creatives. Follow up with meta_ads_creatives_create* to materialize the suggestions after operator review.

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', 'this_month', 'last_month') or explicit 'YYYY-MM-DD..YYYY-MM-DD' (both endpoints inclusive). Longer windows cost more Graph API quota.
Behavior4/5

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

With no annotations provided, the description effectively discloses key behavioral traits: it is read-only, returns ranked suggestions, and does not create creatives. Examples of suggestion content are given, offering transparency about output.

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?

The description is concise (5 sentences) and well-structured: purpose, output examples, behavioral note, and follow-up guidance. Every sentence adds value, with no redundancy or fluff.

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?

Given no output schema and no annotations, the description provides sufficient context: explains return format (ranked list with examples), clarifies computational cost for longer periods, and indicates follow-up tools. It meets the needs for an analysis tool of moderate complexity.

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 the baseline is 3. The description adds context for account_id (optional with fallback) and period (predefined ranges or explicit date format), but these details are already in the schema descriptions. No significant additional meaning beyond the schema.

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?

The description clearly states the tool generates concrete creative-improvement suggestions for a Meta Ads campaign based on performance. The verb 'generates' and resource 'creative-improvement suggestions' are specific, and the tool is well-distinguished from sibling analysis tools like audience, cost, performance, and placements analysis.

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?

The description explicitly includes 'Read-only — does not create creatives' and directs follow-up with 'meta_ads_creatives_create*' after operator review. This provides clear context on when to use the tool (analysis phase) and what to do next, though it does not explicitly state when not to use it.

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