Skip to content
Language — current: English
Theme — current: Match system
Tool
{
  "name": "searchapi_meta_ad_library",
  "description": "Meta Ad Library results from SearchApi, as structured JSON.",
  "input_schema": {
    "type": "object",
    "properties": {
      "q": {
        "type": "string",
        "description": "Search query; most engines accept native operators and advanced filters."
      },
      "country": {
        "type": "string",
        "description": "Country the ads were shown in."
      },
      "platforms": {
        "type": "string",
        "description": "Comma-separated Meta platforms filter: facebook, instagram, audience_network, messenger."
      },
      "media_type": {
        "type": "string",
        "description": "Creative media type filter.",
        "enum": [
          "all",
          "image",
          "video",
          "meme",
          "none"
        ]
      },
      "active_status": {
        "type": "string",
        "description": "Whether the returned ads are currently running.",
        "enum": [
          "all",
          "active",
          "inactive"
        ]
      },
      "ad_type": {
        "type": "string",
        "description": "Ad category filter, e.g. all, political_and_issue_ads."
      },
      "next_page_token": {
        "type": "string",
        "description": "Opaque token from the previous response that fetches the next page."
      }
    },
    "required": [
      "q"
    ],
    "examples": [
      {
        "q": "coffee"
      }
    ]
  }
}

Paste the definition into your own agent's tools array. The schema is generated from this engine's catalog entry, and the reader's configured values ride in the schema's examples. The name is ours rather than the MCP server's — it is what your agent will call — and every engine's is prefixed searchapi_.