meta-ads-mcp

list_custom_audiences

Retrieve custom audiences in your Meta ad account with optional field selection and pagination.

Instructions

List custom audiences in the ad account.

Input Schema

TableJSON Schema

Name	Required	Description
`fields`	No	Comma-separated fields to return
`limit`	No	Number of results (default 25)
`after`	No	Pagination cursor for next page

Implementation Reference

src/tools/audiences.ts:8-8 (registration)
Registration of the 'list_custom_audiences' tool with the MCP server.
```
"list_custom_audiences",
```

src/tools/audiences.ts:10-14 (schema)

Zod schema definition for the tool's input parameters (fields, limit, after).

{
  fields: z.string().optional().describe("Comma-separated fields to return"),
  limit: z.number().optional().default(25).describe("Number of results (default 25)"),
  after: z.string().optional().describe("Pagination cursor for next page"),
},

src/tools/audiences.ts:15-27 (handler)

Handler function that makes a GET request to the Meta Ads API endpoint for listing custom audiences and returns the results.

  async ({ fields, limit, after }) => {
    try {
      const params: Record<string, unknown> = {};
      if (fields) params.fields = fields;
      if (limit) params.limit = limit;
      if (after) params.after = after;
      const { data, rateLimit } = await client.get(`${client.accountPath}/customaudiences`, params);
      return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
    } catch (error) {
      return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
    }
  }
);

src/index.ts:61-61 (registration)
Registration of all audience tools (including list_custom_audiences) at the server level.
```
registerAudienceTools(server, client);
```
src/services/ads-client.ts:180-185 (helper)
The AdsClient.get() helper method used by the handler to make GET requests to the Meta Graph API.
```
async get(
  path: string,
  params?: Record<string, unknown>
): Promise<ClientResponse> {
  return this.request("GET", path, params);
}
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Mar 19, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and scope, omitting pagination behavior, read-only confirmation, rate limits, or whether results include all fields. This is insufficient for a tool with no annotation support.

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 a single, direct sentence with no wasted words. It is concise and front-loaded, stating the action and scope clearly.

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 captures the core purpose but lacks contextual details such as pagination, default field sets, and return format. Given the absence of an output schema and annotations, this leaves some gaps, but for a straightforward list tool it remains minimally viable.

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 does not mention any parameters, but the input schema has 100% coverage with descriptions for 'after,' 'limit,' and 'fields.' Since the schema fully documents parameters, the description adds no extra meaning, meriting the baseline score.

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 uses the specific verb 'List' and identifies the resource 'custom audiences' with clear scope 'in the ad account.' This distinguishes it from sibling tools like list_saved_audiences, which target a different audience type.

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?

No guidance is provided on when to use this tool versus alternatives such as get_audience or list_saved_audiences. There is no mention of exclusions, prerequisites, or recommended scenarios.

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

Deploy Server