Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Facebook Ad Library ad

facebook_adLibrary_ad_get
Read-onlyIdempotent

Fetch a single Facebook Ad Library ad by archive ID or public URL. Use it to retrieve ad details and optional video transcripts for research or verification.

Instructions

Get a single Facebook Ad Library ad by archive id or public Ad Library URL. Optional inputs: adId, url, includeTranscript and trim.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPublic Facebook Ad Library URL for the ad.
adIdNoFacebook Ad Library archive id for the ad.
trimNoWhen true, requests a smaller payload before normalization.
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.
includeTranscriptNoWhen true, includes a plain-text transcript when available for the ad video.

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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that — it never mentions that the tool requires the context/llm_model bookkeeping parameters, that a conversation_id must be echoed before further calls, or how large the returned payload is without trim. With annotations carrying the load, a 3 is fair.

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?

Two short sentences with the core action front-loaded, no filler and no repetition of title boilerplate. The second sentence's parameter list is somewhat redundant with the schema, which keeps 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 read-only get with no output schema, the description never indicates what the response contains (ad creative, metadata, transcript), so an agent cannot anticipate the return shape. It also omits any mention of the mandatory context/llm_model parameters and the conversation_id contract, both of which materially affect correct invocation.

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 adId, url, includeTranscript and trim is already documented in the schema. The description merely enumerates four of the seven optional inputs by name, adding no format, precedence or interaction detail beyond the schema; 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?

The description names a specific verb and resource ('Get a single Facebook Ad Library ad') and the two accepted identifiers, which is enough to separate it from the sibling search tools such as facebook_adLibrary_ads_search_get. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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?

Saying 'by archive id or public Ad Library URL' implies the caller must supply one of the two lookup keys, which is genuinely useful selection context. However, there is no explicit when-to-use versus the ads search tools, no statement about what happens if both or neither identifier is given, and no note on lookup failure behavior.

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