LinkedIn Ads MCP Server

linkedin get campaigns

linkedin_get_campaigns

Read-onlyIdempotent

List LinkedIn ad account campaigns with status, objective, format, bid strategy, budget, and schedule so you can review, filter, and compare them by account, group, name, or type.

Instructions

List campaigns in a LinkedIn ad account with status, objective, format, bid strategy, budget and schedule. On LinkedIn the campaign holds the targeting and the bid, and the creatives under it are the ads.

Input Schema

Name	Required	Description
`name`	No	Exact campaign names to match.
`type`	No	Keep only these campaign formats, such as TEXT_AD or SPONSORED_UPDATES.
`status`	No	Keep only campaigns in these native statuses.
`pageSize`	No	Maximum items in this page, 1 to 100. Defaults to 100.
`pageToken`	No	Opaque nextPageToken from the preceding response; omit for the first page.
`adAccountId`	Yes	Selected LinkedIn advertising account, numeric ID. It must be listed in LINKEDIN_ADS_ACCOUNT_IDS.
`campaignGroupId`	No	Keep only campaigns in this campaign group of the selected account.
`includeTargeting`	No	Return the raw targetingCriteria object. Off by default because it is verbose.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds domain context about where targeting and bids live, but says nothing about pagination, the verbose includeTargeting behavior, or result shape.

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

Conciseness5/5

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

Two tight sentences with the operation and scope front-loaded; the second earns its place by explaining the LinkedIn object hierarchy rather than padding.

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?

With an output schema, full parameter descriptions and rich annotations, the description needs only establish purpose and scope, which it does. A brief note on pagination or the includeTargeting trade-off would close the remaining 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 description coverage is 100%, so every parameter including filters, pageSize/pageToken and includeTargeting is already documented. The description adds no filter syntax or defaults beyond what the schema states, 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?

States a specific verb (list) and resource (campaigns in a LinkedIn ad account) plus the fields surfaced. The second sentence clarifies the campaign-vs-creative hierarchy, which implicitly distinguishes it from linkedin_get_creatives, though no sibling is named outright.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not guidance, and no named alternative among the many siblings (get_campaign_groups, get_creatives, get_insights). The hierarchy note hints at the boundary with creatives but never states it as a selection rule.

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

Deploy Server