Meta Ads by Get MCP Ads

meta get brand safety controls

meta_get_brand_safety_controls

Read-onlyIdempotent

Retrieve brand safety, suitability, placement, and context-control signals from ad account or ad set targeting and block-list metadata. Use this to audit or export existing safety settings.

Instructions

Read brand safety, suitability, placement, and context-control signals from ad account/ad set targeting and optional block-list edges.

Input Schema

TableJSON 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	Pagination cursor from previous response
`adsetIds`	No	Specific ad set IDs to inspect. If omitted, reads ad sets from the ad account.
`businessId`	No	Optional Business Manager ID for block-list discovery.
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`includeAdsets`	No	Include ad set configuration when checking brand safety.
`includeBlockLists`	No	Include accessible brand-safety block-list metadata.
`includeRawTargeting`	No	Include the native targeting specification for diagnostics.

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

A3.8/5.0

Behavior3/5

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

Annotations already carry the behavioral burden with readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description adds modest context about data sources: ad account/ad set targeting and optional block-list edges. The verb 'Read' is consistent with annotations, and there is no contradiction, but no additional behavioral details such as permissions or rate limits are disclosed.

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 a single front-loaded sentence with no filler: it starts with the verb 'Read', identifies the resource, and states the data source scope. Every phrase contributes meaningful selection information.

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 all parameters documented in the schema, an output schema present, and annotations covering safety and mutability, the description is largely complete for an agent to invoke the tool. It conveys the read scope and optional block-list dimension, though it does not explicitly guide selection among sibling read 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 8 parameters with descriptions, types, defaults, and constraints. The description only broadly references block-list edges, matching includeBlockLists, but the schema handles parameter semantics adequately, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Read brand safety, suitability, placement, and context-control signals from ad account/ad set targeting and optional block-list edges.' This is clearly distinct from the sibling tools, none of which mention brand safety or block-list controls.

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 description implies use when brand safety, suitability, placement, or context-control signals are needed, and it names optional block-list edges as part of the scope. However, it does not provide explicit when-to-use vs. when-not-to-use guidance or name alternatives like meta_get_adset_configuration or meta_get_entity_configuration.

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

Deploy Server