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

search_people

Search for LinkedIn profiles using keywords, names, job positions, locations, industries, companies, or schools to find relevant contacts.

Instructions

Allows you to search people applying various filtering criteria (st.searchPeople action).

Input Schema

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

Implementation Reference

  • Registration of SearchPeopleTool in the LinkedApiTools class constructor, where it is instantiated and added to the array of available tools.
    export class LinkedApiTools {
      public readonly tools: ReadonlyArray<LinkedApiTool<unknown, unknown>>;
    
      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),
        ];
      }
  • The SearchPeopleTool class defines the tool name 'search_people', schema for validation, MCP tool definition via getTool(), and delegates execution to the base OperationTool using operationName 'searchPeople' from linkedapi-node.
    export class SearchPeopleTool extends OperationTool<TSearchPeopleParams, unknown> {
      public override readonly name = 'search_people';
      public override readonly operationName = OPERATION_NAME.searchPeople;
      protected override readonly schema = z.object({
        term: z.string().optional(),
        limit: z.number().min(1).max(1000).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(),
          })
          .optional(),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to search people applying various filtering criteria (st.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 10, with a maximum value of 1000.',
              },
              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' },
                  },
                },
              },
            },
          },
        };
      }
    }
  • Base OperationTool class providing the core execute method for all operation-based tools, including search_people. It locates the specific operation by name and executes it with progress tracking.
    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,
        });
      }
    }
  • Zod schema defining the input parameters for the search_people tool, matching TSearchPeopleParams from linkedapi-node.
    protected override readonly schema = z.object({
      term: z.string().optional(),
      limit: z.number().min(1).max(1000).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(),
        })
        .optional(),
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action allows searching with filtering criteria, lacking details on permissions required, rate limits, pagination behavior, or what the search returns (e.g., list of profiles with specific fields). For a search tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that states the tool's function without unnecessary words. However, it includes a parenthetical reference to 'st.searchPeople action', which adds minor clutter without clear value. Overall, it's appropriately sized and front-loaded, with minimal waste.

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 (3 parameters with nested objects) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the search returns (e.g., type of results, fields included) or behavioral aspects like error handling. For a search tool with rich filtering options, more context is needed to guide effective use.

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 input schema fully documents the three parameters (term, limit, filter) and their nested properties. The description adds no additional meaning beyond mentioning 'various filtering criteria', which is already covered by the schema. This meets the baseline of 3, as the schema does the heavy lifting without description enhancement.

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

Purpose3/5

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

The description states the tool 'Allows you to search people applying various filtering criteria', which provides a vague purpose. It mentions the action 'st.searchPeople' but doesn't specify what resource is being searched (e.g., LinkedIn profiles, database records) or distinguish it from sibling tools like 'nv_search_people' or 'fetch_person'. The purpose is understandable but lacks specificity and differentiation.

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 sibling tools like 'nv_search_people' (which appears similar) or 'fetch_person' (which might retrieve a specific person), nor does it specify contexts or prerequisites for use. Without any usage instructions, the agent must infer based on tool names alone.

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