Skip to main content
Glama
rugvedp

All About Ads MCP

search_facebook_ads

Read-only

Search the Facebook Ads Library for live ads by keywords, brand names, or filters. Returns compact previews with an option to retrieve full results from a saved file.

Instructions

Search the Facebook Ads Library for live ads matching the given queries.

Runs a remote scraper (30s–few minutes). Full results are saved to a JSON file; only a compact preview is returned inline. Use read_saved_results to page through the full dataset without flooding context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_typeNoAd type filter: ALL, POLITICAL_AND_ISSUE_ADS, HOUSING_ADS, EMPLOYMENT_ADS, or CREDIT_ADS.ALL
countryNoISO country code to filter by, e.g. 'US', 'IN', or 'ALL'. None for no filter.
sort_byNoSort order: SORT_BY_TOTAL_IMPRESSIONS or SORT_BY_RELEVANCY_MONTHLY_GROUPED.SORT_BY_TOTAL_IMPRESSIONS
end_dateNoLatest ad delivery date in YYYY-MM-DD format. None for no upper bound.
media_typeNoMedia type filter: ALL, IMAGE, MEME, IMAGE_AND_MEME, VIDEO, or NONE.ALL
start_dateNoEarliest ad delivery date in YYYY-MM-DD format. None for no lower bound.
active_statusNoAd status filter: ALL, ACTIVE, or INACTIVE.ALL
search_queriesYesKeywords or brand names to search for, e.g. ['nike', 'adidas'].
content_languagesNoLanguage codes to filter ad content by, e.g. ['en', 'fr'].
publisher_platformsNoPlatforms to filter by, e.g. ['facebook', 'instagram'].
max_results_per_queryNoMaximum ads to return per query. Minimum 10 (actor limit).
enrich_with_ad_detailsNoFetch extra per-ad details. Slower and uses more Apify credits.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
adsYes
queriesYes
file_pathYes
result_countYes
Behavior4/5

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

The description adds behavioral context beyond annotations: it runs a remote scraper with a time estimate, saves full results to a JSON file, and returns only a compact preview. This complements the readOnlyHint and openWorldHint annotations without contradiction.

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 sentences: first states the purpose, second explains the behavior. It is concise, front-loaded, and every sentence adds value.

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?

Given the presence of an output schema, the description adequately covers the tool's behavior, async nature, and file output. Minor gap: lack of clarity on how it relates to start_facebook_ads_scrape, but overall complete.

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 only mentions 'queries' corresponding to the search_queries parameter without adding further details. No extra semantic value beyond the schema.

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 clearly states the tool searches the Facebook Ads Library for live ads matching queries. It distinguishes from siblings like search_google or search_google_ads but does not differentiate from the sibling start_facebook_ads_scrape, which may have a similar purpose.

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 mentions the scraper takes 30s to few minutes and suggests using read_saved_results for full results, implying when to use it. However, it does not explicitly state when not to use it or compare with alternatives like start_facebook_ads_scrape.

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/rugvedp/all-about-ads-mcp'

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