Meta Ads by Get MCP Ads

meta search entities

meta_search_entities

Read-onlyIdempotent

Search campaigns, ad sets, or ads by name within an ad account to locate specific entities. Filter by status to narrow results.

Instructions

Search campaigns, ad sets, or ads by name within an ad account. Useful for finding specific entities.

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
`entityType`	Yes	Type of entity to search
`nameFilter`	Yes	Name substring to search for
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`statusFilter`	No	Filter by native effective_status, not configured status. PAUSED excludes IN_PROCESS, CAMPAIGN_PAUSED and ADSET_PAUSED. Omit for post-creation verification and inspect both returned status fields.

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

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds account-scoped search-by-name behavior, but it does not add extra behavioral details such as substring/case behavior, inclusion of deleted entities, or pagination semantics beyond what the schema already says.

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 short sentences with the key verb and resource front-loaded. The second sentence adds a practical use case without redundant elaboration.

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?

With a fully documented 6-parameter schema, an output schema, and annotations for read-only/idempotent/non-destructive behavior, the description is sufficient for correct invocation. It does not need to describe return values, and no critical operational detail is missing.

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 baseline is 3 even without parameter details in the description. The description does not add meaning beyond the schema, merely restating the name filter and ad account scope.

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 names a specific action (search), resource (campaigns/ad sets/ads), and scope (by name within an ad account), so an agent can grasp what the tool does. It does not explicitly call out how this differs from sibling get/search tools such as meta_get_campaigns or meta_search_targeting_options, so it stops short of full sibling differentiation.

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?

"Useful for finding specific entities" provides an implied use case, but there is no explicit when-to-use/when-not-to-use guidance and no reference to alternative tools among the many sibling list/search tools. An agent must infer when this should be preferred over meta_get_campaigns/meta_get_adsets/meta_get_ads.

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

Deploy Server