Skip to main content
Glama
SocialAPIsHub

SocialAPIs MCP Server

Official

facebook_ads_search

Search Meta Ad Library for ads by keyword or page ID, filtered by country, status, and date range.

Instructions

Search ads in the Meta Ad Library by keyword or page ID with country, status, and date filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch keyword for ads
ad_page_idNoFacebook AD Page ID (alternative to query)
countryNoISO country code or "ALL"
activeStatusNoFilter: ALL, Active, or Inactive
after_timeNoFilter ads after this date (YYYY-MM-DD)
before_timeNoFilter ads before this date (YYYY-MM-DD)
sort_dataNoSort by "impressions" or "recent"
end_cursorNoPagination cursor
Behavior2/5

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

No annotations exist, and the description fails to disclose behavioral traits such as pagination, authentication requirements, rate limits, or the effect of providing no parameters.

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?

A single, efficient sentence that conveys the core purpose without superfluous words.

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

Completeness2/5

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

With 8 optional parameters and no output schema, the description lacks guidance on parameter interdependencies (e.g., query vs. ad_page_id), pagination, and expected return structure, leaving the agent underinformed.

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 coverage is 100%, so the baseline is 3. The description summarizes the filterable fields but adds little meaning beyond the schema's own parameter descriptions.

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 clearly states the tool searches ads by keyword or page ID with filters, and it distinguishes itself from sibling tools like facebook_ads_archive_details and facebook_ads_keywords.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like facebook_ads_archive_details for specific ad details, nor on prerequisites or typical use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SocialAPIsHub/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server