Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

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 and filter campaign setup before managing ads.

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.

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": {
      "adAccountId": "<adAccountId>"
    },
    "name": "linkedin_get_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact campaign names to match.
typeNoKeep only these campaign formats, such as TEXT_AD or SPONSORED_UPDATES.
statusNoKeep only campaigns in these native statuses.
pageSizeNoMaximum items in this page, 1 to 100. Defaults to 100.
pageTokenNoOpaque nextPageToken from the preceding response; omit for the first page.
adAccountIdYesSelected LinkedIn advertising account, numeric ID. It must be listed in LINKEDIN_ADS_ACCOUNT_IDS.
campaignGroupIdNoKeep only campaigns in this campaign group of the selected account.
includeTargetingNoReturn the raw targetingCriteria object. Off by default because it is verbose.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations provide robust technical transparency (read-only, idempotent). The description adds domain-specific behavioral context by explaining that campaigns contain targeting/bidding logic and that creatives are separate, aiding in the agent's conceptual understanding of the LinkedIn ecosystem.

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?

The definition is brief and efficient. It allocates the first sentence to scope and the second to conceptual architectural context, achieving high information density without becoming verbose.

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 100% schema coverage and rich annotations, the description does not need to cover technical details like return types or parameter syntax. It successfully covers the conceptual completeness by describing the data hierarchy (campaign holds targeting, creatives are ads).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given that schema coverage is 100%, the baseline is 3. However, the description adds significant semantic value by clarifying the underlying business logic—specifically, that the campaign object encompasses targeting and bid strategies, which is crucial context for an agent building a complex query.

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?

The purpose is stated clearly as 'List campaigns in a LinkedIn ad account,' immediately identifying the resource and action. The description further enhances this by listing key returned attributes like status, objective, and budget.

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?

While it doesn't explicitly compare itself to siblings, the description details exactly what data is returned (status, objective, format). This helps the agent determine if this tool can fulfill a user's request without needing to call a different tool (e.g., a demographics tool).

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