Skip to main content
Glama
Sign In
Unilytics MCP Server

Unilytics MCP Server

Official
by TeamUnilytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

meta_ads_library

Read-only

Search Meta Ads Library for competitor Facebook and Instagram ads, returning advertiser, ad copy, platforms, dates, and public ad links with cursor-based pagination.

Instructions

Search the Meta Ads Library for competitor ads on Facebook and Instagram.

Returns one page of ads: advertiser page name, creation date, ad copy, link titles and captions, the platforms
it ran on, and a link to the ad's public Ad Library page. `next_cursor` is set when more ads exist; pass it back
as `cursor` (with the same query and country) for the next page.

Args:
    query: Brand or keyword to search (e.g. "Nike", "best crm software")
    country: Two-letter country code (default: "US")
    limit: Max ads per page (default: 25, max: 25)
    cursor: next_cursor from a previous call, for the next page

[Provider: Meta Ad Library API]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "meta_ads_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo
countryNoUS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
-  "default": null,
-  "title": "config",
-  "type": "string"
-}
    • addedInput schema / properties / cursor
      Added value: +{
+  "default": null,
+  "title": "Cursor",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: it lists the returned fields, explains that only one page is returned, and documents the next_cursor pagination contract. It does not mention rate limits or authentication requirements.

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 front-loaded with the tool's purpose and return behavior, followed by a compact Args section that is valuable because the schema has no parameter descriptions. Every sentence supports either selection, invocation, or pagination, with only a minor redundant provider note.

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?

There is no output schema, so the description carries responsibility for return semantics; it does so by listing the fields returned and explaining next_cursor handling. For a simple read-only, four-parameter search tool, this is complete enough to call correctly.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining all four parameters: query with example brand/keyword searches, country as a two-letter code defaulting to US, limit with default 25 and max 25, and cursor as the prior call's next_cursor. This adds substantial meaning beyond the bare input schema.

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 gives a specific verb ('Search') and resource ('Meta Ads Library') and narrows scope to competitor ads on Facebook and Instagram. It is immediately distinguishable from ad-transparency tools for other platforms by the explicit Meta/Facebook/Instagram scope.

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 clearly establishes the use case—searching competitor ads—and explains how to paginate by passing next_cursor back as cursor with the same query and country. It does not explicitly state when not to use this tool or name alternative ad-library tools, but the context is clear.

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