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

nv_search_people

Search for professionals in LinkedIn Sales Navigator using filters like name, company, location, industry, experience, and education to find targeted leads.

Instructions

Allows you to search people in Sales Navigator applying various filtering criteria. (nv.searchPeople action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoOptional. Keyword or phrase to search.
limitNoOptional. Number of search results to return. Defaults to 25, with a maximum value of 2500.
filterNoOptional. Object that specifies filtering criteria for people. When multiple filter fields are specified, they are combined using AND logic.

Implementation Reference

  • Primary implementation of the 'nv_search_people' tool: NvSearchPeopleTool class defining name, operationName, Zod input schema for validation, detailed MCP inputSchema, and getTool() method for tool metadata.
    export class NvSearchPeopleTool extends OperationTool<TNvSearchPeopleParams, unknown> {
      public override readonly name = 'nv_search_people';
      public override readonly operationName = OPERATION_NAME.nvSearchPeople;
      protected override readonly schema = z.object({
        term: z.string().optional(),
        limit: z.number().min(1).max(2500).optional(),
        filter: z
          .object({
            firstName: z.string().optional(),
            lastName: z.string().optional(),
            position: z.string().optional(),
            locations: z.array(z.string()).optional(),
            industries: z.array(z.string()).optional(),
            currentCompanies: z.array(z.string()).optional(),
            previousCompanies: z.array(z.string()).optional(),
            schools: z.array(z.string()).optional(),
            yearsOfExperiences: z.array(z.string()).optional(),
          })
          .optional(),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to search people in Sales Navigator applying various filtering criteria. (nv.searchPeople action).',
          inputSchema: {
            type: 'object',
            properties: {
              term: {
                type: 'string',
                description: 'Optional. Keyword or phrase to search.',
              },
              limit: {
                type: 'number',
                description:
                  'Optional. Number of search results to return. Defaults to 25, with a maximum value of 2500.',
              },
              filter: {
                type: 'object',
                description:
                  'Optional. Object that specifies filtering criteria for people. When multiple filter fields are specified, they are combined using AND logic.',
                properties: {
                  firstName: {
                    type: 'string',
                    description: 'Optional. First name of person.',
                  },
                  lastName: {
                    type: 'string',
                    description: 'Optional. Last name of person.',
                  },
                  position: {
                    type: 'string',
                    description: 'Optional. Job position of person.',
                  },
                  locations: {
                    type: 'array',
                    description:
                      'Optional. Array of free-form strings representing locations. Matches if person is located in any of the listed locations.',
                    items: { type: 'string' },
                  },
                  industries: {
                    type: 'array',
                    description:
                      'Optional. Array of enums representing industries. Matches if person works in any of the listed industries. Takes specific values available in the LinkedIn interface.',
                    items: { type: 'string' },
                  },
                  currentCompanies: {
                    type: 'array',
                    description:
                      'Optional. Array of company names. Matches if person currently works at any of the listed companies.',
                    items: { type: 'string' },
                  },
                  previousCompanies: {
                    type: 'array',
                    description:
                      'Optional. Array of company names. Matches if person previously worked at any of the listed companies.',
                    items: { type: 'string' },
                  },
                  schools: {
                    type: 'array',
                    description:
                      'Optional. Array of institution names. Matches if person 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 person's experience falls within any of the listed ranges.",
                    items: {
                      type: 'string',
                      enum: ['lessThanOne', 'oneToTwo', 'threeToFive', 'sixToTen', 'moreThanTen'],
                    },
                  },
                },
              },
            },
          },
        };
      }
    }
  • Registration of the nv_search_people tool: NvSearchPeopleTool is instantiated (line 59) and added to the LinkedApiTools collection alongside other tools.
    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),
    ];
  • Base handler logic shared by OperationTool subclasses like NvSearchPeopleTool: the execute method locates the LinkedIn API operation by operationName and invokes it via executeWithProgress.
    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,
        });
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'applying various filtering criteria' which hints at functionality, but doesn't describe important behaviors like pagination (only mentions limit parameter), rate limits, authentication requirements, error conditions, or what the response format looks like. For a search tool with no annotation coverage, this is inadequate.

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 - a single sentence that states the core purpose. The parenthetical '(nv.searchPeople action)' adds implementation detail but doesn't significantly detract from clarity. There's no wasted verbiage, though it could be slightly more informative without sacrificing brevity.

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?

Given the complexity (search tool with filtering capabilities), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how results are structured, whether there's pagination beyond the limit parameter, or any error handling. For a search tool that likely returns structured data, this leaves significant gaps for an AI agent.

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 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions 'various filtering criteria' which aligns with the 'filter' parameter, but doesn't provide additional syntax, format details, or usage examples. This meets the baseline expectation when 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's purpose: 'search people in Sales Navigator applying various filtering criteria.' It specifies the verb ('search'), resource ('people'), and context ('Sales Navigator'). However, it doesn't explicitly differentiate from sibling tools like 'search_people' or 'nv_fetch_person', which would be needed for a perfect score.

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. It doesn't mention when to choose this over 'search_people', 'nv_fetch_person', or 'fetch_person', nor does it specify prerequisites or appropriate contexts. The only contextual hint is 'Sales Navigator', but that's part of the purpose statement rather than usage guidance.

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