LinkedIn Ads MCP Server

list_creatives

Retrieve ad creatives from LinkedIn Ads, with optional filtering by campaign ID to focus on specific campaigns.

Instructions

List ad creatives, optionally filtered by campaign.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_creatives"
  }
}

Input Schema

Name	Required	Description	Default
`campaignId`	No

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?

No annotations provided. Description fails to disclose pagination, limits, ordering, or implications of filtering. Additional behavioral traits needed for a list operation.

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

Conciseness3/5

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

Extremely concise at one sentence, but lacks structured details. Could be expanded without being verbose.

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?

Given one optional param and no output schema, the description is incomplete: no mention of return format, pagination, or default behavior (e.g., returns all creatives).

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 has 0% description coverage for 'campaignId' (string). Description mentions 'optionally filtered by campaign' but provides no format, constraints, or behavior details beyond the schema.

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 description 'List ad creatives, optionally filtered by campaign' clearly states the verb (list) and resource (ad creatives), and distinguishes from the sibling 'get_creative' (single) and 'create_ad_creative' (creation).

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 guidance on when to use this tool versus alternatives like 'get_creative' or filtering approaches. No context on prerequisites or exclusions.

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