Skip to main content
Glama
Linked-API

Linked API MCP

by Linked-API
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

fetch_company

Retrieve LinkedIn company details, including basic information and optional employees, posts, or decision makers.

Instructions

Allows you to open a company page to retrieve its basic information (st.openCompanyPage action). Can optionally retrieve employees, posts and decision makers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyUrlYesPublic or hashed LinkedIn URL of the company. (e.g., 'https://www.linkedin.com/company/microsoft')
retrieveEmployeesNoOptional. Whether to retrieve the company's employees information. Default is false.
retrievePostsNoOptional. Whether to retrieve the company's posts information. Default is false.
retrieveDMsNoOptional. Whether to retrieve the company's decision makers information. Default is false.
postsRetrievalConfigNoOptional. Configuration for retrieving posts. Available only if retrievePosts is true.
dmsRetrievalConfigNoOptional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.
employeesRetrievalConfigNoOptional. Configuration for retrieving employees. Available only if retrieveEmployees is true.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.3.4
    • removedInput schema / properties / dmRetrievalConfig
      Removed value: -{
-  "description": "Optional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.",
-  "properties": {
-    "limit": {
-      "description": "Optional. Number of decision makers to retrieve. Defaults to 20, with a maximum value of 20. If a company has fewer decision makers than specified, only the available ones will be returned.",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / dmsRetrievalConfig
      Added value: +{
+  "description": "Optional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.",
+  "properties": {
+    "limit": {
+      "description": "Optional. Number of decision makers to retrieve. Defaults to 20, with a maximum value of 20. If a company has fewer decision makers than specified, only the available ones will be returned.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / employeeRetrievalConfig
      Removed value: -{
-  "description": "Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true.",
-  "properties": {
-    "filter": {
-      "description": "Optional. Object that specifies filtering criteria for employees. When multiple filter fields are specified, they are combined using AND logic.",
-      "properties": {
-        "firstName": {
-          "description": "Optional. First name of employee.",
-          "type": "string"
-        },
-        "industries": {
-          "description": "Optional. Array of enums representing industries. Matches if employee works in any of the listed industries. Takes specific values available in the LinkedIn interface.",
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "lastName": {
-          "description": "Optional. Last name of employee.",
-          "type": "string"
-        },
-        "locations": {
-          "description": "Optional. Array of free-form strings representing locations. Matches if employee is located in any of the listed locations.",
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "position": {
-          "description": "Optional. Job position of employee.",
-          "type": "string"
-        },
-        "schools": {
-          "description": "Optional. Array of institution names. Matches if employee currently attends or previously attended any of the listed institutions.",
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "type": "object"
-    },
-    "limit": {
-      "description": "Optional. Maximum number of employees to retrieve. Defaults to 500, with a maximum value of 500.",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / employeesRetrievalConfig
      Added value: +{
+  "description": "Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true.",
+  "properties": {
+    "filter": {
+      "description": "Optional. Object that specifies filtering criteria for employees. When multiple filter fields are specified, they are combined using AND logic.",
+      "properties": {
+        "firstName": {
+          "description": "Optional. First name of employee.",
+          "type": "string"
+        },
+        "industries": {
+          "description": "Optional. Array of enums representing industries. Matches if employee works in any of the listed industries. Takes specific values available in the LinkedIn interface.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "lastName": {
+          "description": "Optional. Last name of employee.",
+          "type": "string"
+        },
+        "locations": {
+          "description": "Optional. Array of free-form strings representing locations. Matches if employee is located in any of the listed locations.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "position": {
+          "description": "Optional. Job position of employee.",
+          "type": "string"
+        },
+        "schools": {
+          "description": "Optional. Array of institution names. Matches if employee currently attends or previously attended any of the listed institutions.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "limit": {
+      "description": "Optional. Maximum number of employees to retrieve. Defaults to 500, with a maximum value of 500.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / postRetrievalConfig
      Removed value: -{
-  "description": "Optional. Configuration for retrieving posts. Available only if retrievePosts is true.",
-  "properties": {
-    "limit": {
-      "description": "Optional. Number of posts to retrieve. Defaults to 20, with a maximum value of 20.",
-      "type": "number"
-    },
-    "since": {
-      "description": "Optional. ISO 8601 timestamp to filter posts published after the specified time.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / postsRetrievalConfig
      Added value: +{
+  "description": "Optional. Configuration for retrieving posts. Available only if retrievePosts is true.",
+  "properties": {
+    "limit": {
+      "description": "Optional. Number of posts to retrieve. Defaults to 20, with a maximum value of 20.",
+      "type": "number"
+    },
+    "since": {
+      "description": "Optional. ISO 8601 timestamp to filter posts published after the specified time.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / employeeRetrievalConfig / properties / filter / properties / industries / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / employeeRetrievalConfig / properties / filter / properties / locations / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / employeeRetrievalConfig / properties / filter / properties / schools / items
      Added value: +{
+  "type": "string"
+}
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It mentions opening a company page and retrieving info but does not specify if this is read-only, if it has side effects, or what happens to the session. This is adequate but not comprehensive.

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, front-loaded with purpose, no irrelevant information. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (7 parameters, nested objects, no output schema), the description provides a high-level overview but lacks details on the return format or behavior of the 'open' action. It is adequate but could be more complete.

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?

All parameters are well-described in the input schema (100% coverage). The description adds minimal extra meaning beyond listing optional retrievals. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves basic company information with optional employees, posts, and decision makers. It uses a specific verb ('open' and 'retrieve') and resource ('company page'). However, it does not explicitly distinguish from similar tools like 'nv_fetch_company'.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g., search_companies). The description implies using it when you have a company URL, but it does not state prerequisites, ideal scenarios, or conditions to avoid.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Linked-API/linkedapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server