LinkedIn Ads MCP Server

create_saved_audience

Create a new saved audience with custom targeting criteria to reuse in LinkedIn ad campaigns.

Instructions

Create a new saved audience with targeting criteria.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`targetingCriteria`	No	Full LinkedIn targeting criteria object

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Lacks annotations; description only says 'create', which implies mutation, but no mention of permissions, side effects, idempotency, or limits. Insufficient disclosure.

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?

One sentence with no fluff, but could include more detail without being verbose. Efficiency is good, but lacks depth.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, and many siblings. Description fails to explain return value, error conditions, or integration into LinkedIn Ads workflow.

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

Parameters2/5

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

Schema coverage is 50%; description adds no extra meaning beyond schema. Does not explain 'name' purpose or what 'Full LinkedIn targeting criteria object' entails.

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?

Clearly states the verb 'create' and resource 'saved audience' with 'targeting criteria'. Distinguishes from sibling tools like 'delete_saved_audience' and 'update_saved_audience'.

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 indication of when to use this tool versus alternatives like 'create_campaign'. Only describes what it does, not context or prerequisites.

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