LinkedIn Ads MCP Server

linkedin get campaign groups

linkedin_get_campaign_groups

Read-onlyIdempotent

List campaign groups in a LinkedIn ad account with budget, schedule, and serving status to diagnose shared budget or bid strategy issues affecting sibling campaigns.

Instructions

List campaign groups in a LinkedIn ad account, with budget, schedule and serving status. On LinkedIn the campaign group is where a shared budget and a bid strategy live, so it is the level that explains why sibling campaigns stopped together.

Input Schema

Name	Required	Description
`name`	No	Exact campaign group names to match.
`status`	No	Keep only campaign groups 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.

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds that results carry budget, schedule and serving status and explains the LinkedIn hierarchy semantics, though it says nothing about pagination behavior beyond what the schema's pageToken field already conveys.

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 sentences, front-loaded with the action and scope; the second sentence earns its place by supplying domain context that aids tool selection, though it is the kind of background that could be trimmed for a terse agent.

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?

Annotations cover the safety profile and an output schema exists so return values need not be described; with all five parameters documented in the schema, the definition is sufficient for correct invocation, missing only explicit sibling routing.

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%, with name, status, pageSize, pageToken and adAccountId each documented in the schema. The description adds no parameter-level detail (e.g., how name matching or status filtering behaves), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (campaign groups) scoped to a LinkedIn ad account, and the second sentence explains the level's role (shared budget and bid strategy), which distinguishes it from the sibling linkedin_get_campaigns tool without the agent needing to open either schema.

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 phrase 'it is the level that explains why sibling campaigns stopped together' implies when this tool is useful (diagnosing group-level causes), but it never states explicit when-to-use conditions, prerequisites, or an alternative such as linkedin_get_campaigns for campaign-level data.

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

Deploy Server