mcp-linkedin-ads
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_ADS_CLIENT_ID | Yes | OAuth client ID | |
| LINKEDIN_ADS_MCP_WRITE | No | Set to true to expose mutating tools. Read-only by default. | false |
| LINKEDIN_ADS_ACCESS_TOKEN | Yes | OAuth access token | |
| LINKEDIN_ADS_CLIENT_SECRET | Yes | OAuth client secret | |
| LINKEDIN_ADS_REFRESH_TOKEN | No | OAuth refresh token (rotated automatically when set) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_ads_get_client_contextA | Get the current client context and health status based on working directory. Call this first to confirm which LinkedIn Ads account you're working with. |
| linkedin_ads_list_accountsB | List all active LinkedIn Ad Accounts the authenticated user has access to. |
| linkedin_ads_list_campaign_groupsC | List campaign groups for a LinkedIn Ad Account. |
| linkedin_ads_list_campaignsC | List campaigns for a LinkedIn Ad Account, with optional status and campaign group filters. |
| linkedin_ads_campaign_performanceA | Get campaign-level performance metrics (impressions, clicks, spend, conversions, leads, engagement, video views, reach, frequency) for a date range. Reach = approximateMemberReach (unique members exposed); frequency = impressions / reach (computed server-side). This is the main reporting tool for weekly slides. |
| linkedin_ads_account_performanceA | Get account-level aggregate performance metrics for a date range. Good for high-level summaries. Note: reach (approximateMemberReach) and the derived frequency field are not populated at pivot=ACCOUNT; query at CAMPAIGN/CAMPAIGN_GROUP via linkedin_ads_campaign_performance or linkedin_ads_analytics if you need reach. |
| linkedin_ads_analyticsB | Flexible analytics query with custom pivot, fields, and filters. Use for demographic breakdowns, device splits, creative performance, etc. |
| linkedin_ads_list_predictive_audiencesA | List LinkedIn Predictive Audiences (lookalikes) in an ad account: each parent DMP segment with its name, destinations/build status, location filter, seeds and desiredAudienceCount. account_id is required (never taken from the working directory). |
| linkedin_ads_get_predictive_audienceA | Get one LinkedIn Predictive Audience by its parent DMP segment id: name, account, destinations (build status, size), targetingFilter (locations), seeds, desiredAudienceCount and versionTag. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target clearly distinct resources (accounts, campaigns, campaign groups, predictive audiences) and the descriptions explicitly state when to prefer one over another. The trio of campaign_performance, account_performance, and analytics does overlap, but the descriptions differentiate them by pivot/granularity (account-level lacks reach, analytics is the flexible custom query), which mitigates most misselection risk.
All names use a uniform linkedin_ads_ prefix with snake_case, and most follow a verb_noun pattern (list_campaigns, get_client_context, list_predictive_audiences). Minor deviation: campaign_performance and account_performance drop the verb and use noun_noun, and analytics is a bare noun, but the pattern remains readable and predictable.
Nine tools is well within the ideal 3-15 range and each one covers a distinct slice of the reporting surface (context, accounts, campaigns, groups, two performance levels, flexible analytics, two audience lookups). No filler or redundant tools are apparent.
The surface is coherent for a read-only reporting server (accounts, campaigns, groups, performance, predictive audiences), but it is entirely read-only: there is no create/update campaign, no get_campaign or get_campaign_group detail tool, and no ad/creative listing beyond what analytics returns. An agent wanting to drill into a single campaign's settings or manage entities hits a dead end.