Meta Ads by Get MCP Ads

meta list edge raw

meta_list_edge_raw

Read-onlyIdempotent

List allowlisted read-only Meta Graph edges with chosen fields, filters, and cursor pagination to discover entities or fields not covered by specialized tools.

Instructions

List an allowlisted read-only Meta Graph edge with caller-selected flat fields, filters, and cursor pagination. Use this for broad metadata/entity discovery when a specialized tool does not expose a newly added field.

Input Schema

Name	Required	Description
`edge`	Yes	Allowlisted Meta Graph edge to read on the selected node.
`after`	No	Opaque cursor for the next page returned by Meta.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`since`	No	Beginning of the requested reporting period; use the format accepted by the provider.
`until`	No	End of the requested reporting period; use the format accepted by the provider.
`before`	No	Opaque cursor for the previous page returned by Meta.
`fields`	No	Native provider fields to return. Select only fields supported by the chosen object or report.
`parentId`	Yes	Parent Graph node ID, such as act_123, a Business, Page, catalog, campaign, or ad set ID
`filtering`	No	Native provider filter expressions; credentials and account overrides are not allowed.
`parameters`	No	Additional documented GET parameters, for example targeting_spec or optimization_goal; auth and HTTP method override parameters are blocked
`includeSummary`	No	Request the provider's available summary or total-count metadata.

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.

Changed7 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / filtering / items / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / parameters / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / until / $ref
```
Removed value: -"#/properties/since"
```
addedInput schema / properties / until / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
addedInput schema / properties / until / type
```
Added value: +"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

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds useful traits: the edge allowlist and 'flat fields' (i.e., no nested expansion), plus cursor pagination. It does not mention rate limits, error modes, or what the allowlist rejects.

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?

Two sentences, zero filler, with the capability statement first and the routing guidance second. Nothing to trim.

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?

Output schema exists, so return values need no explanation, and the schema fully covers the 11 parameters including the blocked-parameter constraints. For a generic escape-hatch tool this is nearly complete; only guidance on which edges pair with which parentId types is absent.

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% and every parameter (edge, parentId, fields, filtering, parameters, cursors, since/until) is documented in the schema. The description only restates the categories of input without adding format details, so baseline 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?

Specific verb+resource: 'List an allowlisted read-only Meta Graph edge' paired with the field/filter/pagination capabilities. It distinguishes itself from the specialized siblings by framing itself as the generic discovery path, though the term 'edge' remains jargon that only the schema enum fully disambiguates.

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?

Explicitly says when to use it ('broad metadata/entity discovery when a specialized tool does not expose a newly added field'), which implicitly tells the agent to prefer specialized tools first. No explicit when-not or named alternative, so it falls short of the top band.

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

Deploy Server