Skip to main content
Glama

meta_ads_audiences_create_lookalike

Create a lookalike audience from a source audience, targeting a specific country with a similarity ratio between 1% and 20% to expand reach while maintaining match quality.

Instructions

Creates a Lookalike Audience from an existing source audience. Returns the new audience_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Lookalikes typically populate within 24–72h; the approximate_count remains 0 until Meta finishes the similarity build. ratio=0.01 gives the top 1% most similar users in the target country (smallest, highest match); ratio=0.10 gives top 10% (larger reach, looser match). For the base audience list use meta_ads_audiences_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAudience name shown in Ads Manager. Must be unique within the account.
ratioYesSimilarity ratio — fraction of the target country's population to include. 0.01 = top 1% (tightest match, smallest audience); 0.20 = top 20% (loosest, largest). Meta caps at 0.20.
countryYesTarget country ISO code(s) for the lookalike expansion. Accepts a single code string (e.g. 'JP') or a list (e.g. ['JP', 'KR']). Lookalike reach is always scoped to the specified country/countries.
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.
starting_ratioNoLower bound of the ratio range. Default 0.0. Advanced: set > 0 to carve out a tiered lookalike that excludes the top-similarity slice (e.g. starting_ratio=0.01, ratio=0.05 = users ranked 1–5% in similarity, excluding the top 1%).
source_audience_idYesSource Custom Audience to build the lookalike from. Meta recommends a source of at least 1,000–10,000 users for good match quality.
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: mutating operation, not automatically reversible, populates within 24-72h, approximate_count remains 0 until ready, ratio meaning and ranges, starting_ratio advanced usage. No contradictions.

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?

Single paragraph but well-organized: starts with purpose and return, then mutation warning, timing, ratio explanation, parameter notes, and sibling reference. Could be slightly more structured but concise with no redundant sentences.

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?

Covers creation, return value, timing, ratio details, starting_ratio, source recommendation, and rollback suggestion. Lacks error cases or permissions, but no output schema exists and parameters are well documented. Adequately complete for the tool's function.

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

Parameters5/5

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

Schema has 100% description coverage, but the description adds significant value: explains ratio ranges (0.01=top1%,0.10=top10%), starting_ratio advanced use, country accepts single or list, source audience size recommendation, account_id fallback, name uniqueness. Goes well beyond bare 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?

Clearly states it creates a Lookalike Audience from an existing source and returns the new audience_id. Distinguishes from sibling meta_ads_audiences_list by explicitly directing users to that tool for listing base audiences.

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?

Provides explicit when-to-use: creating a lookalike. Directs to meta_ads_audiences_list for listing base audiences. Also recommends recording before-state for rollback via mureo_state_action_log_append. Lacks explicit exclusion of other audience creation tools but the name and context suffice.

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