Meta Ads by Get MCP Ads

meta list edge raw

meta_list_edge_raw

Read-onlyIdempotent

List read-only Meta Graph edges using custom fields, filters, and pagination to retrieve metadata when specialized tools miss newly added fields.

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

TableJSON 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

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

First observedv2.0.1Sep 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'read-only' is consistent with them. The description adds meaningful context beyond annotations by disclosing the 'allowlisted' edge restriction and the fallback role for newly added fields. It does not discuss auth or rate limits, but the output schema and read-only annotations cover the main safety profile.

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 carry the full message: first the core behavior and mechanism, then the use-case guidance. There is no filler, repetition of schema details, or unnecessary prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complex 11-parameter schema, 100% schema coverage, full annotations, and an output schema, the description is complete enough. It explains the operation, the allowlist constraint, and when to fall back to this tool rather than a specialized sibling, leaving no material gap an agent needs to call it correctly.

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 every parameter having a description, enum, bounds, or pattern, so the baseline is 3. The description's phrase 'caller-selected flat fields, filters, and cursor pagination' loosely maps to the fields, filtering, before, after, and limit parameters, but adds no meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb and resource: 'List an allowlisted read-only Meta Graph edge', and adds caller-selected fields, filters, and cursor pagination. It further distinguishes itself from specialized siblings by describing the tool as broad metadata/entity discovery for newly added fields, making selection unambiguous.

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 description explicitly states when to use this tool: broad metadata/entity discovery when a specialized tool does not expose a newly added field, which implies specialized tools are preferred when they do cover the need. It does not name specific sibling tools or give explicit 'do not use for X' exclusions, so it is clear but not fully exhaustive.

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

Deploy Server