Meta Ads by Get MCP Ads

meta get organic content enrichment

meta_get_organic_content_enrichment

Read-onlyIdempotent

Read Facebook Page posts and Instagram media with URLs, date filters, and optional content insights to support organic reporting and performance review.

Instructions

Read Facebook Page posts and Instagram media with URLs, native periods and optional insights. These are content insights, not Ads Insights; do not infer an organic-only breakdown.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`since`	No	Optional Graph time filter. For IG media this should be Unix seconds or strtotime-compatible text.
`until`	No	Optional Graph time filter. For IG media this should be Unix seconds or strtotime-compatible text.
`cursor`	No	Pagination cursor from previous response
`pageId`	No	Facebook Page ID for /posts and linked IG discovery.
`postIds`	No	Specific Facebook post IDs to enrich.
`mediaIds`	No	Specific Instagram media IDs to enrich.
`includeInsights`	No	Include available insight metrics; additional provider permissions may be required.
`includePagePosts`	No	Read related Facebook Page posts when the token has permission.
`instagramAccountId`	No	Instagram professional account ID for /media.
`includeInstagramMedia`	No	Read related Instagram media when the token has permission.

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.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds scope context about content versus ads insights, but does not add permission details, rate-limit behavior, or pagination context beyond what the schema provides.

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 two tight sentences with no wasted wording. The primary purpose is front-loaded, and the second sentence adds a targeted disambiguation warning.

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 schema coverage and an output schema, the description is nearly complete for selection and invocation. Its main remaining gap is sibling routing: it distinguishes Ads Insights but not the adjacent organic-content or page-post 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 all 11 parameters are already documented in the schema. The description only adds high-level meaning around URLs, native periods, and optional insights, without explaining parameter relationships or selection logic.

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 a specific verb and resources: reading Facebook Page posts and Instagram media enriched with URLs, native periods, and optional insights. It clearly distinguishes this from Ads Insights, though it does not name or disambiguate against the close sibling meta_get_page_posts.

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?

It gives a useful exclusion: these are content insights, not Ads Insights, and warns not to infer an organic-only breakdown. However, it does not say when to use this tool instead of siblings such as meta_get_page_posts or meta_get_insights.

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

Deploy Server