LinkedIn MCP Server

get_organizations

Retrieve a list of organizations you manage on LinkedIn. Use this to view organizations where you have administrative access.

Instructions

List organizations the user administers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_organizations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/organization/index.ts:15-31 (handler)

Handler function that executes the get_organizations tool logic by calling the LinkedIn client.

export async function handleOrganizationTool(name: string, args: any, client: LinkedInClient) {
  switch (name) {
    case "get_organizations": {
      const result = await client.getOrganizations();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
    default:
      throw new McpError(ErrorCode.MethodNotFound, `Unknown organization tool: ${name}`);
  }
}

src/tools/organization/index.ts:4-13 (schema)

Tool schema definition for get_organizations with name, description, and input schema (no inputs).

export const organizationTools = [
  {
    name: "get_organizations",
    description: "List organizations the user administers.",
    inputSchema: {
      type: "object",
      properties: {},
    },
  },
];

src/index.ts:76-78 (registration)
Registration of the get_organizations tool in the CallToolRequestSchema handler, routing to handleOrganizationTool.
```
if (organizationTools.some((t) => t.name === name)) {
  return await handleOrganizationTool(name, args, linkedinClient);
}
```

src/index.ts:47-55 (registration)

Registration of organizationTools (including get_organizations) in the ListToolsRequestSchema handler.

server.setRequestHandler(ListToolsRequestSchema, async () => {
  return {
    tools: [
      ...profileTools,
      ...contentTools,
      ...networkTools,
      ...organizationTools,
    ],
  };

src/linkedin-client.ts:106-109 (helper)
Helper method in LinkedInClient that makes the actual API call to LinkedIn's /organizationAcls endpoint.
```
async getOrganizations() {
  const response = await this.client.get("/organizationAcls?q=roleAssignee");
  return response.data;
}
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 16, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Without annotations, the description should disclose behaviors like authentication needs or pagination, but it only says 'list organizations', lacking any behavioral context.

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?

The description is a single, concise sentence with no extraneous information, earning its place efficiently.

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?

For a simple list tool with no params or output schema, the description is adequate but minimal. It could specify return format or the meaning of 'administers' for full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so the description cannot add parameter meaning. The baseline score of 4 is appropriate as the description is sufficient for param semantics.

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

Purpose5/5

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

The description clearly states the tool lists organizations the user administers, using specific verb and resource. It is easily distinguishable from sibling tools like create_article_post or get_connections.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when to list organizations versus retrieving profiles or connections.

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

Deploy Server