Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_adLibrary_search_companies

Search Facebook Ad Library pages by company name to retrieve page IDs for ad lookups, plus likes and Instagram details.

Instructions

facebookAdLibrary: Search for Companies. GET /v1/facebook/adLibrary/search/companies. Search Ad Library pages by name and get each page id for /v1/facebook/adLibrary/company/ads, with likes and Instagram details. An empty result costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when searchResults is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": "facebook_adLibrary_search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany or page name to search for (up to 200 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the billing rules in detail: 0 credits on empty results, 1 credit on success, 0 for errors, blocked or timed-out requests, invalid requests and cache hits. That is genuinely useful context beyond the schema. Gaps remain on authentication requirements, and on how an empty response is detected beyond the mention of searchResults.

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

Conciseness3/5

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

The purpose is front-loaded and the endpoint is given early, but the credit-cost material sprawls across several sentences and repeats itself (an empty result costing 0 is stated twice, along with a separate restatement about not-found results). Consolidating the pricing rules into a single sentence would remove real redundancy.

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?

There are no annotations and no output schema, so the description must cover the return values; it does so at a high level (page IDs, likes, Instagram details). It is nearly complete for a single-parameter search tool, with only the shape of the response objects and any authentication preconditions left unspecified.

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%, and the single 'query' parameter is already documented as a company or page name with a 200-character limit. The description adds no matching or formatting hints beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource ('Search for Companies', 'Search Ad Library pages by name') and clarifies both the output ('page id', 'likes and Instagram details') and the follow-up route ('for /v1/facebook/adLibrary/company/ads'). An agent can distinguish this from facebook_adLibrary_company_ads, which consumes the IDs this tool returns.

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 implies the workflow: use this to find page IDs, then feed them to the company/ads endpoint. There is no explicit statement of when-not to use it, or which sibling to prefer for ad-level or keyword searches, but the context is clear enough for correct selection.

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