Meta Ads by Get MCP Ads

meta get business assets

meta_get_business_assets

Read-onlyIdempotent

Discover accessible Meta Business assets read-only, including businesses, pages, Instagram accounts, pixels, and datasets, so you can identify resources available to your permissions.

Instructions

Discover accessible Meta Business assets read-only: businesses, pages, Instagram accounts, pixels, and datasets when permissions allow.

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.
`cursor`	No	Legacy cursor for /me/businesses only. Use cursors for asset edges.
`cursors`	No	Per-edge cursors from paging/nextActions. Never reuse a cursor for another edge.
`maxPages`	No	Maximum pages per edge; remaining pages are reported explicitly.
`businessId`	No	Business Manager ID. With adAccountId, discover only its owning Business; otherwise list /me/businesses when this is omitted.
`adAccountId`	No	Optional ad account ID to discover its owner Business and assigned pixels; datasets are read from that Business when permitted.

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
```
addedInput schema / properties / cursors / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

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 cover readOnly/idempotent/non-destructive/openWorld, and the description adds a genuinely non-structured fact: that each asset class is returned only 'when permissions allow', warning the agent not to treat an empty section as proof of absence. It does not explain what happens on permission failure (error vs. omission) or describe paging behavior, but the safety profile is already carried by 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?

A single front-loaded sentence that packs the verb, the resource, the enumerated asset types, the read-only guarantee and the permission caveat with zero filler. Nothing is restated or padded.

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?

With a full input schema and an output schema present, the description need not explain parameters or return shape; it covers scope and the permission caveat, which is what's missing from structured fields. The only shortfall is that it does not hint that passing businessId/adAccountId switches the tool into a narrower owner-discovery mode.

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 limit, cursor, cursors, maxPages, businessId and adAccountId are all fully documented in the schema, which sets the baseline at 3. The description mentions no parameter at all — not even the businessId/adAccountId scoping that materially changes what is discovered — so it adds nothing beyond the schema.

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 ('Discover') plus a named resource class ('Meta Business assets') and enumerates the concrete asset types returned: businesses, pages, Instagram accounts, pixels, datasets. This lets an agent understand it is a broad cross-asset discovery tool, though it never names the narrower siblings (meta_get_pages, meta_get_pixels, meta_get_instagram_accounts) it overlaps with.

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 clause 'when permissions allow' signals that results are conditional, which implies usage context, but there is no explicit statement of when to prefer this tool over the per-asset siblings like meta_get_pages or meta_get_pixels. An agent must infer that this is the umbrella discovery tool versus the targeted listing tools.

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

Deploy Server