Skip to main content
Glama

meta_ads_audiences_create_lookalike

Create a Lookalike Audience from a source audience to reach new users similar to your existing customers. Specify target country and similarity ratio (0.01–0.20) to control match quality and reach. Returns the new audience ID.

Instructions

Creates a Lookalike Audience from an existing source audience. Returns the new audience_id. Mutating, reversible via rollback_apply. 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
account_idYesMeta 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.
nameYesAudience name shown in Ads Manager. Must be unique within the account.
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.
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.
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.
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%).
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses mutation, reversibility via rollback_apply, population latency (24-72h), and ratio impact on match quality. Lacks authentication or rate limit details but covers key behaviors.

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?

Four sentences front-loaded with purpose and return value, then behavioral notes, then ratio explanation, then sibling reference. Every sentence adds value; no redundancy.

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?

Covers return type (audience_id), mutation reversibility, population behavior, ratio interpretation, source audience size hint, and sibling tool. No gaps for a create tool with no output schema.

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?

All 6 parameters have schema descriptions (100% coverage). Description adds extra meaning: ratio values with percentages, starting_ratio advanced usage, country flexibility, and source_audience_id size recommendation. Enriches parameter understanding.

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 explicitly says 'Creates a Lookalike Audience from an existing source audience' with a clear verb and resource, and mentions the return value (audience_id). It is distinct from sibling tools like meta_ads_audiences_create and meta_ads_audiences_list.

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 sibling reference ('For the base audience list use meta_ads_audiences_list') and explains when lookalike is appropriate (similarity ratio semantics, population time). However, it does not explicitly state when not to use or alternative tools for other audience types.

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