Skip to main content
Glama
Sign In

LinkedIn Ads MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted LinkedIn Ads MCP server, with each action switched on or off per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/linkedin-ads-mcp-server
GitHub Stars
1
Server Listing
LinkedIn Ads MCP Server
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation3/5

execute_action and query_data are both labeled as Step 3 final tools and require nearly identical prerequisite workflows, making their boundary depend mainly on the distinction between 'action' and 'query'. query_contexts and prompts_menu are distinct, but the two final tools could be confused when available_actions includes both query and action items.

Naming Consistency3/5

All names use snake_case, but the conventions are mixed: query_contexts and query_data share a query_ prefix, execute_action is verb_noun, and prompts_menu is noun_noun. The names are readable but not a predictable pattern across the set.

Tool Count4/5

Four tools is a focused, workflow-oriented set: metadata/planning via query_contexts, read queries via query_data, action execution via execute_action, and prompt catalog browsing via prompts_menu. It is slightly thin, but each tool has a role and the count fits a gateway-style LinkedIn Ads server.

Completeness4/5

The surface covers discovery/metadata, action details, data querying, action execution, and prompt browsing, which supports the stated workflow. There are minor gaps such as no explicit prompt creation/update and no dedicated account/brand management tools, but these may be outside scope or handled through execute_action.

Available Tools

4 tools
execute_actionLinkedIn Ads Execute ActionA
Destructive
Inspect

Execute LinkedIn Ads action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuLinkedIn Ads PromptsA
Read-only
Inspect

Browse the LinkedIn Ads prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsLinkedIn Ads Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe LinkedIn Ads data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, ad_account_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataLinkedIn Ads Data QueryA
Read-only
Inspect

Query LinkedIn Ads data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • linkedin-ads-mcp

      dhawalshah
      A
      license
      B
      quality
      C
      maintenance
      LinkedIn Ads MCP server with full read/write campaign management, Ad Library competitive search, and Cloud Run team deployment.
      25
      8 npm
      MIT

    • heyreagent

      linglistack
      F
      license
      Not graded
      quality
      C
      maintenance
      Hosted LinkedIn MCP server that connects AI apps to a user's own LinkedIn account, enabling inbox reading, messaging, invitations, people search, and post interactions.
      2
      -

    • SalesTouch

      antoineDsh
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.
      2
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources