meta-ads-mcp-server

Overview Schema Source Related Servers Discussions Admin

meta get audience details

meta_get_audience_details

Read-onlyIdempotent

Retrieve detailed custom, saved, and lookalike audiences from Meta Ads, with pagination and rich fields where permissions allow.

Instructions

Read detailed custom, saved, and lookalike audiences with pagination and rich fields where permissions allow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Provider object or operation type selected from this schema's allowed values.	all
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`cursor`	No	Pagination cursor from previous response
`adAccountId`	No	Ad account ID used when listing audiences.
`audienceIds`	No	Specific audience IDs to fetch via batch IDs lookup.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.0Sep 30, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results."

addedInput schema / properties / type / description

Added value: +"Provider object or operation type selected from this schema's allowed values."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedv1.0.0Aug 29, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description adds useful behavioral context beyond the readOnly and destructive annotations: it discloses pagination support and that rich fields depend on permissions. It avoids contradicting any annotation, and 'where permissions allow' helps set expectations about partial data.

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?

A single compact sentence that front-loads the core purpose ('Read detailed ... audiences') and then adds two key behaviors (pagination, permission-dependent fields). Every word earns its place and there is no redundancy.

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?

The schema fully documents parameters, annotations cover safety, and an output schema exists, so the description does not need to explain return values. It covers the essential scope, pagination, and permission nuance, but the lack of guidance on choosing this over meta_get_audiences leaves a slight completeness gap 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?

With 100% schema description coverage, the schema already documents all five parameters, including constraints and defaults. The description itself adds no parameter-specific meaning, so the baseline of 3 is appropriate; it has zero effect on parameter clarity.

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 it reads detailed custom, saved, and lookalike audiences, naming both the resource and action. It hints at being the detailed counterpart to other audience tools, but it does not explicitly differentiate from the sibling meta_get_audiences.

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 given about when to use this tool over alternatives such as meta_get_audiences. The description implies it serves detailed audience reads, but it does not state exclusions, prerequisites, or which sibling to prefer for simpler queries.

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

Deploy Server