Skip to main content
Glama
Sign In
Meta MCP Server

Meta MCP Server

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Lookalike Audience

meta_create_lookalike_audience

Creates a lookalike audience from a source custom audience, targeting users similar to existing customers in a specified country with a defined size ratio.

Instructions

Creates a lookalike audience based on an existing custom audience or page.

Args:

  • ad_account_id (string): Ad account ID

  • name (string): Audience name

  • origin_audience_id (string): Source custom audience ID to base the lookalike on

  • country (string): ISO 3166-1 alpha-2 country code (e.g., "US", "GB")

  • ratio (number): Lookalike size as fraction of country population (0.01–0.20, i.e. 1%–20%)

Returns the new lookalike audience ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_account_id": "<ad_account_id>",
      "name": "<name>",
      "origin_audience_id": "<origin_audience_id>",
      "country": "<country>",
      "ratio": "<ratio>"
    },
    "name": "meta_create_lookalike_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_account_idYes
nameYes
origin_audience_idYesSource custom audience ID
countryYesISO country code (e.g., US)
ratioYesAudience size ratio (0.01–0.20)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations indicate a non-read-only, non-idempotent mutation. The description confirms it creates a new resource and returns its ID, adding the prerequisite that it relies on an existing custom audience or page. It does not detail error conditions or side effects beyond creation, which is acceptable given the annotations.

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?

The description is concise and well-structured, starting with the main purpose and then listing arguments in a clear, readable format. It avoids extraneous detail and includes a brief return statement, making it easy for an agent to parse.

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

Completeness3/5

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

The description covers all required parameters and the return value, but it does not explicitly differentiate this tool from sibling audience tools or mention the optional response_format. It also assumes knowledge of prerequisites without elaboration, leaving some context gaps for an agent.

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?

The description adds meaning to ratio (range and explanation), origin_audience_id (source), and country (examples), which are beneficial since the schema lacks descriptions for ad_account_id and name. However, it omits the optional response_format parameter, though that is covered in the schema.

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

Purpose4/5

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

The description clearly states that the tool creates a lookalike audience based on an existing custom audience or page, which is a specific and distinct action. It differentiates from sibling audience tools by the term 'lookalike', though the mention of 'page' is not fully reflected in the parameter description for origin_audience_id.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like meta_create_custom_audience or meta_create_saved_audience. It only describes what it does without specifying conditions, exclusions, or when to prefer it over other audience-creation tools.

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

Deploy Server

Other Tools