LinkedIn Ads MCP Server

create_sponsored_post

Create a sponsored post (dark post) for use as ad creative, not appearing in your feed. Returns a share URN for creating ad creatives.

Instructions

Create a sponsored post (dark post) for use as ad content. This post won't appear in the org's feed — it's only used as ad creative. Returns a share URN to pass to create_ad_creative. REQUIRES w_organization_social OAuth scope — if you get ACCESS_DENIED, add this scope to your LinkedIn app and re-authorize.

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

Input Schema

Name	Required	Description
`commentary`	Yes	Ad copy / post text
`imageAssetUrn`	No	Image asset URN from upload_image (e.g. urn:li:digitalmediaAsset:XXX)
`landingPageUrl`	No	Click-through URL for the ad
`title`	No	Link preview title (shown below image)
`description`	No	Link preview description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that the post won't appear in feed, is only for ad creative, returns a share URN, and requires specific OAuth scope. Does not discuss rate limits or side effects, but adequate for a basic creation tool.

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 sentences that are front-loaded: first sentence states purpose, second explains usage and OAuth requirement. No unnecessary words, highly efficient.

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?

Given 5 parameters, no output schema, and no annotations, the description provides essential information about purpose, return value, and prerequisite OAuth scope. Lacks error handling details but is sufficient for an agent to select and invoke correctly.

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 has 100% description coverage, so baseline is 3. Description adds context about the return value and OAuth scope but does not enhance parameter meanings beyond schema descriptions.

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?

Explicitly states 'Create a sponsored post (dark post) for use as ad content' and clarifies it won't appear in the org's feed. Distinguishes from sibling create_full_ad by specifying it's only for ad creative.

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

Usage Guidelines4/5

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

Clearly explains the tool is for creating ad content, not feed posts, and directs to pass the return URN to create_ad_creative. Mentions required OAuth scope for troubleshooting, but doesn't explicitly exclude other use cases.

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