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 and filter results by status.

Instructions

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

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

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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

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

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds account scoping and name-based search context but does not disclose rate limits, result behavior, pagination implications, or status-filter semantics beyond what structured fields provide.

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 purpose front-loaded and a brief usage note. There is no redundant or filler content.

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?

An output schema exists and the input schema richly documents pagination, limits, enums, and status-filter nuances, so the description need not repeat those. It gives the core scope and search intent, though it omits routing guidance versus the sibling get/list 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%, with all six parameters documented, including enum values and the statusFilter caveat about native effective_status. The description only restates that entities are searched by name and type, adding no extra parameter meaning such as case sensitivity or exact-match behavior.

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 states a specific verb ('Search') and resources (campaigns, ad sets, ads), scoped to an ad account and by name. It does not explicitly distinguish this search behavior from sibling list/get tools such as meta_get_campaigns or meta_get_ads, so it stops short of a 5.

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?

It gives an implied usage context with 'Useful for finding specific entities,' suggesting use when a name is known. It provides no explicit when-not guidance, alternatives, or notes about pagination versus list-style sibling tools.

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

Deploy Server