Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Facebook ad library companies

facebook_adLibrary_companies_search
Read-onlyIdempotent

Search Facebook Ad Library for companies or advertisers by name and return a matching list. Use it to find advertiser pages before reviewing their ad activity.

Instructions

Search Facebook Ad Library companies / advertisers by name. Requires query. Returns a list.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_adLibrary_companies_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Search query text for Facebook ad library companies.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only the return shape ("Returns a list"), which is genuinely useful since no output schema exists, but says nothing about result caps, pagination, or rate limits.

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?

Three short sentences, front-loaded with the search action and resource, with no filler. "Requires `query`" mildly duplicates the schema's required array, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only search with full schema coverage and rich annotations, the essentials are present. It still omits how many results come back, whether pagination exists, and the multi-call conversation_id handshake that the schema gestures at, which matters for an open-world search.

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 every parameter including query, context, llm_model and conversation_id is already documented in the schema. The description only restates that query is required, adding no syntax or format guidance beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ("Search Facebook Ad Library companies / advertisers by name"), which separates it from the ad-level siblings like facebook_adLibrary_ads_search_get and facebook_adLibrary_ad_get. It does not explicitly name an alternative, but the resource is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied only: it tells the agent the lookup is by name, which hints at how to form the query. There is no statement of when to prefer this over the google/linkedin/tiktok advertiser searches, and no exclusions or prerequisites.

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