Skip to main content
Glama
getmcpads-com

meta-ads-mcp-server

by getmcpads-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

meta get audiences

meta_get_audiences
Read-onlyIdempotent

List custom, saved, and lookalike audiences for a Meta ad account, with optional type filters, to review targeting options for ad campaigns.

Instructions

List custom, saved, and lookalike audiences for a Meta ad account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by audience type
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
adAccountIdYesAd account ID (e.g., act_123456789)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed2 schema fields changedv2.0.0
    • 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."
    • 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"
+}
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'List' wording is consistent with those. The description adds no extra behavioral context like pagination limitations, rate limits, or the meaning of open-world results, but the annotations carry most of the safety burden.

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 front-loaded sentence that directly states the verb, resource, and scope with zero filler. Every word contributes meaning, and the size is appropriate for this simple list-type tool.

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?

Given the full parameter descriptions, complete output schema, and annotations covering read-only/idempotent behavior, the description is mostly sufficient. It could have pointed to meta_get_audience_details for single-audience lookups, but the core calling context is adequately covered by the schema and annotations.

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?

Schema description coverage is 100%, so all three parameters are already documented in the schema. The description's mention of custom/saved/lookalike mirrors the enum for 'type' and adds no new meaning beyond the schema; 'limit' and 'adAccountId' are fully covered by their schema descriptions.

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 uses the specific verb 'List' with the resource 'audiences' and names the three audience types (custom, saved, lookalike) plus the ad account scope. It clearly differentiates the list-level function from a detail-level tool like meta_get_audience_details, though it does not name that sibling explicitly.

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 guidance on when to use this tool versus siblings such as meta_get_audience_details or other audience-related tools. There are no alternatives named, no exclusions, and no context indicating when a user should choose a different tool.

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