Skip to main content
Glama
thenavidm

Facebook Ad Library MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Look at an ad's images

view_ad_creative
Read-onlyIdempotent

Return the actual images from one ad to inspect visual hooks, layouts, product shots, and text placement instead of reading only its copy; carousels return cards in order.

Instructions

Return the actual images from one ad so you can see them, rather than only reading its copy. Use this when the question is about what an ad looks like: the visual hook, the layout, the product shot, how the text sits on the image, or what several ads have in common visually. A carousel returns each card in order. Video ads have no still to show and report that instead. Needs no API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many images to return, up to 6. Carousels have several.
countryNoTwo-letter country code. Default US.
library_idYesThe Ad Library ID, from search_ads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for the extra behavior it discloses: carousels return each card in order, video ads have no still and report that instead, and it needs no API key. These edge cases and auth details go well beyond structured fields.

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?

Front-loaded with the core action, followed by when-to-use, then edge-case behavior in compact sentences. Every sentence carries distinct information with no filler.

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 no output schema, the description compensates by explaining return shape for carousels (each card in order) and the video-ad exception, and annotations carry the safety profile. Nothing needed to invoke it correctly 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 library_id, country, and limit are already fully documented, including the 'up to 6' limit and 'Carousels have several' note. The description adds no param syntax or format detail beyond that, making the baseline 3 correct.

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+resource: 'Return the actual images from one ad.' It distinguishes itself functionally from copy-reading siblings via 'rather than only reading its copy,' which implies the contrast with get_ad, though no sibling is named outright.

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

Usage Guidelines4/5

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

It gives concrete trigger conditions: 'Use this when the question is about what an ad looks like: the visual hook, the layout, the product shot...'. Strong when-to-use guidance, but no explicit when-not or named alternative such as get_ad for text-only questions.

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

Deploy Server

Other Tools