Meta Ads by Get MCP Ads

meta get entity configuration

meta_get_entity_configuration

Read-onlyIdempotent

Read a specific ad entity's fields from its ad account for reconciliation. Verify field-level accuracy before claiming an exact match.

Instructions

Read a specific entity in its ad account for reconciliation. Read-only; never creates, changes or retries the entity. Missing or normalized fields must be inspected before claiming an exact match.

Input Schema

Name	Required	Description
`fields`	Yes	Exact fields to re-read from the reviewed native creation payload. IDs and account ownership are always checked.
`entityId`	Yes	Exact entity ID saved in the acknowledged creation receipt.
`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.

Changed3 schema fields changedv2.1.1Oct 30, 2026

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

changedInput schema / properties / fields / items / enum

Previous value: -[
-  "name",
-  "status",
-  "objective",
-  "daily_budget",
-  "lifetime_budget",
-  "special_ad_categories",
-  "special_ad_category_country",
-  "bid_strategy",
-  "campaign_id",
-  "optimization_goal",
-  "billing_event",
-  "targeting",
-  "promoted_object",
-  "bid_amount",
-  "bid_constraints",
-  "start_time",
-  "end_time",
-  "attribution_spec",
-  "destination_type",
-  "is_dynamic_creative",
-  "dsa_beneficiary",
-  "dsa_payor",
-  "adset_id",
-  "creative",
-  "tracking_specs",
-  "conversion_domain",
-  "object_story_spec",
-  "asset_feed_spec",
-  "object_story_id",
-  "instagram_actor_id",
-  "instagram_user_id",
-  "url_tags",
-  "degrees_of_freedom_spec",
-  "is_adset_budget_sharing_enabled"
-]New value: +[
+  "name",
+  "status",
+  "objective",
+  "daily_budget",
+  "lifetime_budget",
+  "special_ad_categories",
+  "special_ad_category_country",
+  "bid_strategy",
+  "campaign_id",
+  "optimization_goal",
+  "billing_event",
+  "targeting",
+  "promoted_object",
+  "bid_amount",
+  "bid_constraints",
+  "start_time",
+  "end_time",
+  "attribution_spec",
+  "destination_type",
+  "is_dynamic_creative",
+  "dsa_beneficiary",
+  "dsa_payor",
+  "adset_id",
+  "creative",
+  "tracking_specs",
+  "conversion_domain",
+  "object_story_spec",
+  "asset_feed_spec",
+  "object_story_id",
+  "instagram_actor_id",
+  "instagram_user_id",
+  "url_tags",
+  "degrees_of_freedom_spec",
+  "is_adset_budget_sharing_enabled",
+  "applink_treatment",
+  "omnichannel_link_spec"
+]

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.8/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, but the description adds useful behavioral context: it never creates, changes, or retries the entity, and it warns that missing or normalized fields must be inspected before claiming an exact match. This goes beyond restating 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, front-loads the core purpose, and includes only directly relevant caveats. Every sentence contributes to understanding or safe use.

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 are rich, so the description need not explain return values or safety guarantees in depth. It adds a reconciliation caveat and normalization warning, though it still leaves some ambiguity about which entity types this covers relative to sibling tools.

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 the schema already documents all three required parameters, including the fields enum and ID formats. The description does not add parameter-specific meaning beyond the schema, so the baseline score 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?

The description states a specific verb and resource: reading a specific entity in its ad account for reconciliation. It is clear enough to understand the operation, but it does not distinguish this generic entity read from specific sibling tools such as meta_get_adset_configuration or meta_get_campaign_structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "for reconciliation" implies the intended use case, and the note about missing or normalized fields provides a workflow caveat. However, it does not explicitly say when to use this tool versus sibling configuration readers or when not to use it.

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

Deploy Server