Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn Ad Library ad

linkedin_adLibrary_ad_get
Read-onlyIdempotent

Retrieve a LinkedIn Ad Library ad by its ad ID or public URL to inspect ad details and verify campaign creative. Use either identifier to resolve the specific ad record.

Instructions

Get a LinkedIn Ad Library ad by ad id or Ad Library URL. Optional inputs: adId and url.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPublic LinkedIn Ad Library URL for the ad.
adIdNoLinkedIn Ad Library id for the ad.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds the useful fact that adId and url are both optional alternatives, but does not say what ad data comes back, whether either key alone suffices, or what happens when both are supplied.

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, front-loaded with the purpose before the inputs. Efficient with no filler, though the second sentence is close to redundant with the schema.

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?

No output schema exists and the description does not describe return values, which is a real gap for an open-world lookup tool. With no output schema, the agent gets no hint of what an ad record contains or how it is shaped.

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 is documented in the schema itself and the baseline is 3. The description only restates that adId and url are optional, adding essentially no semantics beyond the schema.

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?

Names a specific verb (Get) and resource (LinkedIn Ad Library ad) plus the two lookup keys (adId, URL), which lets an agent distinguish this detail lookup from the sibling search-list tool. It stops short of explicitly naming the search alternative for differentiation.

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?

The description implies usage by noting a lookup by id or URL, so an agent can infer this is the single-ad detail fetch rather than a discovery call. It never states when to use this versus linkedin_adLibrary_ads_search_list, nor any precondition such as requiring an id obtained from a prior search.

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