mcp-linkedin_ads

LinkedIn Ads MCP Pack

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool	Description
`li_list_ad_accounts`	Check which LinkedIn ad accounts you can access. Returns account IDs, names, and status to identify which account to use for campaigns.
`li_list_campaigns`	Get all campaigns in a LinkedIn ad account (e.g., account ID "501234567"). Returns campaign IDs, names, budgets, status, and date ranges.
`li_get_campaign`	Get full details for a specific LinkedIn campaign (e.g., campaign ID "501234567"). Returns name, budget, spend, status, targeting, and performance metrics.
`li_campaign_analytics`	Analyze campaign performance over a date range (e.g., "2024-01-01" to "2024-01-31"). Returns impressions, clicks, conversions, spend, and CTR by campaign.
`li_list_creatives`	View all ads in a LinkedIn campaign (e.g., campaign ID "501234567"). Returns creative IDs, titles, content, status, and creation dates to compare variations.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

config.json

{
  "mcpServers": {
    "linkedin_ads": {
      "url": "https://gateway.pipeworx.io/linkedin_ads/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/linkedin_ads/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

config.json

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

Code

ask_pipeworx({ question: "your question about Linkedin_ads data" })

The gateway picks the right tool and fills the arguments automatically.

License

MIT

Linkedin Ads README