Meta Ads by Get MCP Ads

meta get adset configuration

meta_get_adset_configuration

Read-onlyIdempotent

Read an existing ad set's native settings, parent campaign budget/objective, account currency, and cross-channel creative requirements before editing or adding ads; no mutation.

Instructions

Read an existing ad set, its parent campaign budget/objective and account currency before preparing an edit or adding ads. For a web and app (cross-channel) ad set, creativeRequirements gives the applink_treatment (and omnichannel_link_spec) used by its own ads. Returns native settings; no mutation.

Input Schema

Name	Required	Description	Default
`adSetId`	Yes	Exact Meta ad set ID in the selected advertising account.
`adAccountId`	Yes	Owning advertising account ID. Use the exact ID returned by account discovery; do not substitute a campaign or business ID.

Output 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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so 'no mutation' is largely redundant, but 'returns native settings' adds genuinely new context (values are raw platform values, not normalized) and the creativeRequirements/applink_treatment note discloses a non-obvious field for cross-channel ad sets. That goes beyond what the annotations convey.

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?

Three short sentences, front-loaded with the action and use case, then the cross-channel caveat. The closing 'Returns native settings; no mutation' partially repeats the readOnly annotation, which is the only wasted clause.

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?

An output schema exists and annotations cover safety, so the description needn't explain return format. It supplies the pre-edit use case and the cross-channel creativeRequirements nuance, leaving only minor gaps such as what 'native settings' excludes or how errors surface.

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% with both adSetId and adAccountId fully documented, including the warning not to substitute campaign or business IDs. The description adds no parameter-level detail of its own, so the baseline of 3 applies.

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?

States a specific verb (Read) and resource (an existing ad set) and broadens scope to parent campaign budget/objective and account currency, which tells the agent exactly what payload to expect. It does not name a sibling such as meta_get_adsets or meta_get_entity_configuration to sharpen the distinction, so it falls short of 5.

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?

The phrase 'before preparing an edit or adding ads' gives a concrete trigger condition, which is real usage guidance rather than a restatement of the name. It stops at positive guidance and never says when to prefer a sibling or when this read is unnecessary.

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

Deploy Server