Skip to main content
Glama
Linked-API
by Linked-API

nv_fetch_company

Retrieve company information from LinkedIn Sales Navigator, including optional employee and decision maker data with configurable filters.

Instructions

Allows you to open a company page in Sales Navigator to retrieve its basic information (nv.openCompanyPage action). Can optionally retrieve employees and decision makers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyHashedUrlYesHashed LinkedIn URL of the company.
retrieveEmployeesNoOptional. Whether to retrieve the company's employees information. Default is false.
retrieveDMsNoOptional. Whether to retrieve the company's decision makers information. Default is false.
employeeRetrievalConfigNoOptional. Configuration for retrieving employees. Available only if retrieveEmployees is true.
dmRetrievalConfigNoOptional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.

Implementation Reference

  • The OperationTool base class implements the execute method, which is the core handler logic for running the 'nvFetchCompany' operation from the LinkedIn API.
    export abstract class OperationTool<TParams, TResult> extends LinkedApiTool<TParams, TResult> {
      public abstract readonly operationName: TOperationName;
    
      public override execute({
        linkedapi,
        args,
        workflowTimeout,
        progressToken,
      }: {
        linkedapi: LinkedApi;
        args: TParams;
        workflowTimeout: number;
        progressToken?: string | number;
      }): Promise<TMappedResponse<TResult>> {
        const operation = linkedapi.operations.find(
          (operation) => operation.operationName === this.operationName,
        )! as Operation<TParams, TResult>;
        return executeWithProgress(this.progressCallback, operation, workflowTimeout, {
          params: args,
          progressToken,
        });
      }
    }
  • The specific NvFetchCompanyTool class that configures the 'nv_fetch_company' tool with name, operationName, Zod schema, and MCP Tool definition.
    export class NvFetchCompanyTool extends OperationTool<TNvFetchCompanyParams, unknown> {
      public override readonly name = 'nv_fetch_company';
      public override readonly operationName = OPERATION_NAME.nvFetchCompany;
      protected override readonly schema = z.object({
        companyHashedUrl: z.string(),
        retrieveEmployees: z.boolean().optional().default(false),
        retrieveDMs: z.boolean().optional().default(false),
        employeeRetrievalConfig: z
          .object({
            limit: z.number().min(1).max(500).optional(),
            filter: z
              .object({
                firstName: z.string().optional(),
                lastName: z.string().optional(),
                positions: z.array(z.string()).optional(),
                locations: z.array(z.string()).optional(),
                industries: z.array(z.string()).optional(),
                schools: z.array(z.string()).optional(),
                yearsOfExperiences: z.array(z.string()).optional(),
              })
              .optional(),
          })
          .optional(),
        dmRetrievalConfig: z
          .object({
            limit: z.number().min(1).max(20).optional(),
          })
          .optional(),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to open a company page in Sales Navigator to retrieve its basic information (nv.openCompanyPage action). Can optionally retrieve employees and decision makers.',
          inputSchema: {
            type: 'object',
            properties: {
              companyHashedUrl: {
                type: 'string',
                description: 'Hashed LinkedIn URL of the company.',
              },
              retrieveEmployees: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the company's employees information. Default is false.",
              },
              retrieveDMs: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the company's decision makers information. Default is false.",
              },
              employeeRetrievalConfig: {
                type: 'object',
                description:
                  'Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true.',
                properties: {
                  limit: {
                    type: 'number',
                    description:
                      'Optional. Maximum number of employees to retrieve. Defaults to 500, with a maximum value of 500.',
                  },
                  filter: {
                    type: 'object',
                    description:
                      'Optional. Object that specifies filtering criteria for employees. When multiple filter fields are specified, they are combined using AND logic.',
                    properties: {
                      firstName: {
                        type: 'string',
                        description: 'Optional. First name of employee.',
                      },
                      lastName: {
                        type: 'string',
                        description: 'Optional. Last name of employee.',
                      },
                      positions: {
                        type: 'array',
                        description:
                          "Optional. Array of job position names. Matches if employee's current position is any of the listed options.",
                        items: { type: 'string' },
                      },
                      locations: {
                        type: 'array',
                        description:
                          'Optional. Array of free-form strings representing locations. Matches if employee is located in any of the listed locations.',
                        items: { type: 'string' },
                      },
                      industries: {
                        type: 'array',
                        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' },
                      },
                      schools: {
                        type: 'array',
                        description:
                          'Optional. Array of institution names. Matches if employee currently attends or previously attended any of the listed institutions.',
                        items: { type: 'string' },
                      },
                      yearsOfExperiences: {
                        type: 'array',
                        description:
                          "Optional. Array of enums representing professional experience. Matches if employee's experience falls within any of the listed ranges.",
                        items: {
                          type: 'string',
                          enum: ['lessThanOne', 'oneToTwo', 'threeToFive', 'sixToTen', 'moreThanTen'],
                        },
                      },
                    },
                  },
                },
              },
              dmRetrievalConfig: {
                type: 'object',
                description:
                  'Optional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.',
                properties: {
                  limit: {
                    type: 'number',
                    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.',
                  },
                },
              },
            },
            required: ['companyHashedUrl'],
          },
        };
      }
    }
  • Registers the NvFetchCompanyTool instance in the LinkedApiTools collection's tools array, likely used for MCP tool provision.
    constructor(progressCallback: (progress: LinkedApiProgressNotification) => void) {
      this.tools = [
        // Standard tools
        new SendMessageTool(progressCallback),
        new GetConversationTool(progressCallback),
        new CheckConnectionStatusTool(progressCallback),
        new RetrieveConnectionsTool(progressCallback),
        new SendConnectionRequestTool(progressCallback),
        new WithdrawConnectionRequestTool(progressCallback),
        new RetrievePendingRequestsTool(progressCallback),
        new RemoveConnectionTool(progressCallback),
        new SearchCompaniesTool(progressCallback),
        new SearchPeopleTool(progressCallback),
        new FetchCompanyTool(progressCallback),
        new FetchPersonTool(progressCallback),
        new FetchPostTool(progressCallback),
        new ReactToPostTool(progressCallback),
        new CommentOnPostTool(progressCallback),
        new CreatePostTool(progressCallback),
        new RetrieveSSITool(progressCallback),
        new RetrievePerformanceTool(progressCallback),
        // Sales Navigator tools
        new NvSendMessageTool(progressCallback),
        new NvGetConversationTool(progressCallback),
        new NvSearchCompaniesTool(progressCallback),
        new NvSearchPeopleTool(progressCallback),
        new NvFetchCompanyTool(progressCallback),
        new NvFetchPersonTool(progressCallback),
        // Other tools
        new ExecuteCustomWorkflowTool(progressCallback),
        new GetWorkflowResultTool(progressCallback),
        new GetApiUsageTool(progressCallback),
      ];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the action 'nv.openCompanyPage' but doesn't describe what 'basic information' includes, how data is returned, whether there are rate limits, authentication requirements, or potential side effects. The description is insufficient for a tool with complex nested parameters and no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with two sentences that efficiently convey the core functionality and optional features. It's front-loaded with the main purpose, though it could be slightly more structured by separating mandatory and optional behaviors.

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

Completeness2/5

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

For a tool with 5 parameters (including complex nested objects), no annotations, and no output schema, the description is inadequate. It doesn't explain what 'basic information' includes, how results are structured, or provide any context about the Sales Navigator environment. The agent would struggle to understand what this tool actually returns or how to interpret results.

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?

Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds minimal value by mentioning the optional retrieval of employees and decision makers, but doesn't provide additional context beyond what's in the parameter descriptions. This meets the baseline for high schema coverage.

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's purpose: 'open a company page in Sales Navigator to retrieve its basic information' with optional retrieval of employees and decision makers. It specifies the verb ('open', 'retrieve') and resource ('company page', 'basic information', 'employees', 'decision makers'), but doesn't explicitly differentiate from sibling tools like 'fetch_company' or 'search_companies'.

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 like 'fetch_company', 'search_companies', or 'nv_search_companies'. It mentions optional parameters but doesn't explain when to use them or any prerequisites for using the tool effectively.

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