Skip to main content
Glama

LinkedIn Ad Search

linkedin_ad_search

[Acquire · 10 credits] Search the LinkedIn ad library. Useful for tracking competitor ad creative and messaging. Costs 10 credits per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linkedin_ad_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNoCompany name or LinkedIn slug to filter ads
refreshNoBypass the cache and re-run the search live (costs 10 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
keywordsNoKeyword filter applied to ad creative

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, destructiveHint=false, readOnlyHint=false and idempotentHint=false; the description's real addition is the 10-credit billing fact, which matters before a paid call. It says nothing about caching semantics despite the schema's refresh parameter governing cached results, nor about result limits or latency. Useful but thin beyond the cost note.

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 credit cost is stated twice — once in the bracketed "[Acquire · 10 credits]" tag and again as "Costs 10 credits per call" — which is avoidable duplication in an otherwise short definition. The lead is front-loaded, but one of the three sentences earns nothing.

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?

With no output schema, the definition gives no sense of what an ad record contains (creative, copy, advertiser, dates) or whether results are paginated. Coverage of cost and purpose is adequate for a simple three-parameter search, but the omission of return shape leaves a gap.

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 schema descriptions for company, keywords, and refresh (including the cache-bypass cost behavior) are already detailed. The description adds no parameter-level meaning, so the baseline of 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?

"Search the LinkedIn ad library" gives a specific verb and resource, and the ad-library scope distinguishes it from sibling searches such as linkedin_post_search or linkedin_company_search. It does not explicitly name an alternative or state what makes the ad library different, but the resource itself 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?

"Useful for tracking competitor ad creative and messaging" supplies one concrete use case, which implies when to reach for it. There is no when-not guidance and no reference to any sibling tool for other search needs, so an agent must infer the boundaries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources