Skip to main content
Glama

LinkedIn Ad Library Ad Details

social_linkedin_ad
Read-only

Retrieves detailed information about a specific LinkedIn ad by URL. Returns id, description, headline, adType, advertiser, and targeting with language, location, and audience criteria. Also includes totalImpressions, impressionsByCountry, adDuration, startDate, and endDate. Date and impression fields are nullable when LinkedIn does not expose them on the public ad page. The existing image, video, organicVideo, preRollVideo, and carouselImages fields keep their previous values. paidForBy is the public paying entity when LinkedIn shows one, without the 'Paid for by' prefix. targetingTable lists the public targeting-category flags that LinkedIn shows; it does not expand a collapsed location summary into individual locations. imageSources and thumbnailSources list the creative-image and video-poster URLs LinkedIn supplies. videoSources lists native video renditions as { src, type, bitrate }; preRollVideoSources uses the same structure but contains only pre-roll ad video. type and bitrate are null when absent; bitrate is in bits per second. Choose the lowest positive bitrate for a smaller video download, rather than assuming source order ranks quality. All four source fields are arrays and are empty when unavailable. Document-cover previews are included in imageSources where available, including search fallback results. LinkedIn may expose only one image or thumbnail resolution; URLs are signed and should not be rewritten to guess smaller sizes. Search detail hydration is best-effort, so blocked or timed-out detail fetches can leave videoSources empty even for a video ad. No extra parameter or credit charge is required. adDuration is the ad availability date-range text, not video playback duration; it is an empty string with null startDate/endDate when LinkedIn does not publish the availability block. Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. LinkedIn Ad Library Ad Details API View Pricing Get ad details and native media variants where available. LinkedIn may expose only one image or thumbnail size. 1 credit per request Retrieves detailed information about a specific LinkedIn ad by URL. Returns id, description, headline, adType, advertiser, and targeting with language, location, and audience criteria. Also includes totalImpressions, impressionsByCountry, adDuration, startDate, and endDate. Date and impression fields are nullable when LinkedIn does not expose them on the public ad page. The existing image, video, organicVideo, preRollVideo, and carouselImages fields keep their previous values. paidForBy is the public paying entity when LinkedIn shows one, without the 'Paid for by' prefix. targetingTable lists the public targeting-category flags that LinkedIn shows; it does not expand a collapsed location summary into individual locations. imageSources and thumbnailSources list the creative-image and video-poster URLs LinkedIn supplies. videoSources lists native video renditions as { src, type, bitrate }; preRollVideoSources uses the same structure but contains only pre-roll ad video. type and bitrate are null when absent; bitrate is in bits per second. Choose the lowest positive bitrate for a smaller video download, rather than assuming source order ranks quality. All four source fields are arrays and are empty when unavailable. Document-cover previews are included in imageSources where available, including search fallback results. LinkedIn may expose only one image or thumbnail resolution; URLs are signed and should not be rewritten to guess smaller sizes. Search detail hydration is best-effort, so blocked or timed-out detail fetches can leave videoSources empty even for a video ad. No extra parameter or credit charge is required. adDuration is the ad availability date-range text, not video playback duration; it is an empty string with null startDate/endDate when LinkedIn does not publish the availability block.

Input Schema

NameRequiredDescriptionDefault
urlYesThe url of the ad

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare read-only/open-world safety, and the description goes well beyond that: nullable date and impression fields, empty-array semantics for the four source fields, signed URLs that must not be rewritten, best-effort hydration that can leave videoSources empty even for a video ad, and the caveat that adDuration is an availability range rather than playback duration. The one real defect is the self-contradictory credit pricing (10 credits vs. 1 credit per request), which leaves an agent unable to predict cost.

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

Conciseness2/5

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

The description is roughly twice as long as necessary because the entire field-by-field paragraph is duplicated verbatim, and it also splices in page chrome ('LinkedIn Ad Library Ad Details API View Pricing... 1 credit per request'). The valuable semantics are buried mid-paragraph rather than front-loaded, and the contradictory credit statements waste the reader's attention.

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 is no output schema, so the description must carry the return-value burden, and it does so thoroughly: enumerated fields, nullability, array-empty behavior, bitrate units, and the distinction between native and pre-roll video sources. What is missing is pricing consistency and any note on URL format or failure modes beyond the 'blocked or timed-out detail fetches' remark.

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?

With one parameter at 100% schema description coverage, the schema already documents 'url'. The description adds only the phrase 'by URL'; it does not clarify whether a full LinkedIn Ad Library URL is required, whether canonical/shortened forms are accepted, or what happens with a URL for a non-existent ad. Baseline 3 applies when the schema carries the parameter burden.

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 opening sentence gives a specific verb and resource ('Retrieves detailed information about a specific LinkedIn ad by URL'), which distinguishes it from the search sibling social_linkedin_ads_search by the URL-keyed, single-ad scope. However, no sibling is named explicitly, and the repeated second copy of the paragraph plus injected marketing text ('API View Pricing Get ad details...') muddies an otherwise crisp statement.

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 only implied: 'by URL' signals that this is the follow-up call once you already have an ad URL, presumably from social_linkedin_ads_search. There is no explicit when-to-use / when-not-to-use statement and no named alternative. The cost sentences further confuse rather than guide, since the description variously says 'No extra parameter or credit charge is required', 'at least 10 Nexscope credits', and '1 credit per request'.

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.