Adsap

Show Ad Library Ad

adsap_get_ad_library_snapshot

SHOW what Ad Library ads ACTUALLY LOOK LIKE (creative, copy, page name), in a SELF-CONTAINED card. Pass up to 8 ad ids in ad_ids and ONE call renders them all as a gallery the user can click through; pass one id for a single full-size ad. Video ads PLAY in the card and carousel ads show their slides. Use this right after adsap_search_ad_library whenever the user asks to SEE or SHOW ads: a table of links shows nothing, so render the top results (up to 8) in the SAME turn instead of offering to. One call takes about 8 seconds whatever the number of ads, so always batch: never call once per ad. This is public ad-transparency data, not your own ads (for those use adsap_get_ad_preview). It renders ads exactly as the Ad Library shows them, so it works only for ads that search returned in the first place.

Input Schema

TableJSON Schema

Name	Required	Description
`ad_id`	No	A single Ad Library ad id. Same as ad_ids with one entry; prefer ad_ids.
`ad_ids`	No	The Ad Library ad ids to show, 1 to 8, taken from adsap_search_ad_library results' `id` field, in the order you want them displayed (e.g. highest reach first). Two or more render as a gallery. For more than 8 ads, show the first 8 and call again for the next ones when the user asks.
`ad_account_id`	Yes	Your ad account ID (act_xxx) — the same one used for the adsap_search_ad_library call. Anchors the workspace ownership check and the Meta budget.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

changedInput schema / properties / ad_id / description

Previous value: -"The Ad Library ad id to render, taken from an adsap_search_ad_library result's `id` field (also shown as 'Library ID' on the ad itself). Numeric."New value: +"A single Ad Library ad id. Same as ad_ids with one entry; prefer ad_ids."

addedInput schema / properties / ad_ids

Added value: +{
+  "description": "The Ad Library ad ids to show, 1 to 8, taken from adsap_search_ad_library results' `id` field, in the order you want them displayed (e.g. highest reach first). Two or more render as a gallery. For more than 8 ads, show the first 8 and call again for the next ones when the user asks.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "ad_account_id",
-  "ad_id"
-]New value: +[
+  "ad_account_id"
+]

First observedSep 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden — and it does: timing (~8 seconds regardless of count), rendering behavior (video ads play, carousels show slides, clickable gallery), and a real constraint that it only works for ads search returned. It also discloses the workspace ownership/budget anchoring via ad_account_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the first sentence and every sentence carries operational value. It is dense (multi-clause sentences joined by semicolons) and longer than strictly necessary, but there is little waste.

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?

For a rendering tool with no output schema, the description fully covers what the agent must know: input shape, batching rules, timing, visual behavior, and the dependency on prior search results. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds genuine meaning beyond the schema: order of ad_ids controls display order (e.g. highest reach first), 2+ render as a gallery vs 1 as full-size, prefer ad_ids over ad_id, and the >8 overflow workflow. This is more than the schema alone conveys.

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?

States a specific verb+resource: render Ad Library ads (creative, copy, page name) in a self-contained card/gallery. It explicitly distinguishes itself from sibling tools, noting this is public ad-transparency data and pointing to adsap_get_ad_preview for the user's own ads. An agent can tell it apart without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('right after adsap_search_ad_library whenever the user asks to SEE or SHOW ads'), when-not/alternative routing (adsap_get_ad_preview for own ads), and operational rules (batch up to 8, render in the same turn, never call once per ad). Nothing is left to inference.

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

All Adsap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?