Skip to main content
Glama
Sign In

LinkedIn Pages MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted LinkedIn Pages 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-pages-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation4/5

The four tools have mostly distinct roles: query_contexts is a planning/discovery helper, query_data retrieves data, execute_action performs actions, and prompts_menu browses prompts. However, query_data and execute_action share nearly identical prerequisite workflow text and are both labeled 'Step 3 (FINAL)', which creates some risk of misselection.

Naming Consistency4/5

All names use snake_case, giving a consistent style. Most follow a verb_noun pattern (query_contexts, query_data, execute_action), with prompts_menu being the minor noun_noun deviation.

Tool Count4/5

Four tools is a reasonable, well-scoped set for this workflow-oriented server: one helper, one data query, one action executor, and one prompt browser. It is slightly lean but not obviously missing a separate tool.

Completeness4/5

The generic execute_action and query_data tools appear to cover the broad LinkedIn Pages action/data surface, while query_contexts provides discovery and prompts_menu covers prompt catalog/detail access. Minor gaps might exist around more explicit validation or lifecycle management, but core workflows are covered.

Available Tools

4 tools
execute_actionLinkedIn Pages Execute ActionA
Destructive
Inspect

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

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_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 Pages PromptsA
Read-only
Inspect

Browse the LinkedIn Pages 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 Pages Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe LinkedIn Pages data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_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 Pages Data QueryB
Read-only
Inspect

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

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_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-company-admin-mcp

      negrueu
      A
      license
      A
      quality
      D
      maintenance
      MCP server for LinkedIn Company Page administration. Enables reading analytics, managing posts, editing page details, growing followers, and bridging personal profile for employee advocacy workflows.
      24
      MIT

    • LinkedIn MCP Server

      abdulrehmanzahid160
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for interacting with the LinkedIn API, enabling profile lookup, post creation and deletion, image posting, and organization page management through a secure tool-based interface.
      -

    • 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

    • LinkedIn MCP Server

      selvin-paul-raj
      A
      license
      A
      quality
      D
      maintenance
      Fully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.
      6
      4
      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