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

fetch_person

Retrieve LinkedIn profile information including basic details, with optional data for experience, education, skills, languages, posts, comments, and reactions.

Instructions

Allows you to open a person page to retrieve their basic information and perform additional person-related actions if needed. (st.openPersonPage action). Allows additional optional retrieval of experience, education, skills, languages, posts, comments and reactions. āš ļø PERFORMANCE WARNING: Only set additional retrieval flags to true if you specifically need that data. Each additional parameter significantly increases execution time: šŸ’” Recommendation: Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
personUrlYesThe LinkedIn profile URL of the person to fetch (e.g., 'https://www.linkedin.com/in/john-doe')
retrieveExperienceNoOptional. Whether to retrieve the person's experience information. Default is false.
retrieveEducationNoOptional. Whether to retrieve the person's education information. Default is false.
retrieveSkillsNoOptional. Whether to retrieve the person's skills information. Default is false.
retrieveLanguagesNoOptional. Whether to retrieve the person's languages information. Default is false.
retrievePostsNoOptional. Whether to retrieve the person's posts information. Default is false.
retrieveCommentsNoOptional. Whether to retrieve the person's comments information. Default is false.
retrieveReactionsNoOptional. Whether to retrieve the person's reactions information. Default is false.
postsRetrievalConfigNoOptional. Configuration for retrieving posts. Available only if retrievePosts is true.
commentRetrievalConfigNoOptional. Configuration for retrieving comments. Available only if retrieveComments is true.
reactionRetrievalConfigNoOptional. Configuration for retrieving reactions. Available only if retrieveReactions is true.

Implementation Reference

  • The execute method of OperationTool provides the core handler logic for the fetch_person tool. It resolves the LinkedAPI operation using the tool's operationName (OPERATION_NAME.fetchPerson) and executes it with progress notifications.
    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 input schema for validating parameters to the fetch_person tool, used in the validate method.
    protected override readonly schema = z.object({
      personUrl: z.string(),
      retrieveExperience: z.boolean().optional().default(false),
      retrieveEducation: z.boolean().optional().default(false),
      retrieveSkills: z.boolean().optional().default(false),
      retrieveLanguages: z.boolean().optional().default(false),
      retrievePosts: z.boolean().optional().default(false),
      retrieveComments: z.boolean().optional().default(false),
      retrieveReactions: z.boolean().optional().default(false),
      postsRetrievalConfig: z
        .object({
          limit: z.number().min(1).max(20).optional(),
          since: z.string().optional(),
        })
        .optional(),
      commentRetrievalConfig: z
        .object({
          limit: z.number().min(1).max(20).optional(),
          since: z.string().optional(),
        })
        .optional(),
      reactionRetrievalConfig: z
        .object({
          limit: z.number().min(1).max(20).optional(),
          since: z.string().optional(),
        })
        .optional(),
    });
  • MCP Tool specification including name 'fetch_person', detailed description, and JSON inputSchema matching the zod schema.
      public override getTool(): Tool {
        return {
          name: this.name,
          description: `Allows you to open a person page to retrieve their basic information and perform additional person-related actions if needed. (st.openPersonPage action). Allows additional optional retrieval of experience, education, skills, languages, posts, comments and reactions.
    āš ļø **PERFORMANCE WARNING**: Only set additional retrieval flags to true if you specifically need that data. Each additional parameter significantly increases execution time:
    šŸ’” **Recommendation**: Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task.
    `,
          inputSchema: {
            type: 'object',
            properties: {
              personUrl: {
                type: 'string',
                description:
                  "The LinkedIn profile URL of the person to fetch (e.g., 'https://www.linkedin.com/in/john-doe')",
              },
              retrieveExperience: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's experience information. Default is false.",
              },
              retrieveEducation: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's education information. Default is false.",
              },
              retrieveSkills: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's skills information. Default is false.",
              },
              retrieveLanguages: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's languages information. Default is false.",
              },
              retrievePosts: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's posts information. Default is false.",
              },
              retrieveComments: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's comments information. Default is false.",
              },
              retrieveReactions: {
                type: 'boolean',
                description:
                  "Optional. Whether to retrieve the person's reactions information. Default is false.",
              },
              postsRetrievalConfig: {
                type: 'object',
                description:
                  'Optional. Configuration for retrieving posts. Available only if retrievePosts is true.',
                properties: {
                  limit: {
                    type: 'number',
                    description:
                      'Optional. Number of posts to retrieve. Defaults to 20, with a maximum value of 20.',
                  },
                  since: {
                    type: 'string',
                    description:
                      'Optional. ISO 8601 timestamp to filter posts published after the specified time.',
                  },
                },
              },
              commentRetrievalConfig: {
                type: 'object',
                description:
                  'Optional. Configuration for retrieving comments. Available only if retrieveComments is true.',
                properties: {
                  limit: {
                    type: 'number',
                    description:
                      'Optional. Number of comments to retrieve. Defaults to 20, with a maximum value of 20.',
                  },
                  since: {
                    type: 'string',
                    description:
                      'Optional. ISO 8601 timestamp to filter comments made after the specified time.',
                  },
                },
              },
              reactionRetrievalConfig: {
                type: 'object',
                description:
                  'Optional. Configuration for retrieving reactions. Available only if retrieveReactions is true.',
                properties: {
                  limit: {
                    type: 'number',
                    description:
                      'Optional. Number of reactions to retrieve. Defaults to 20, with a maximum value of 20.',
                  },
                  since: {
                    type: 'string',
                    description:
                      'Optional. ISO 8601 timestamp to filter reactions made after the specified time.',
                  },
                },
              },
            },
            required: ['personUrl'],
          },
        };
  • Registers FetchPersonTool as part of the LinkedApiTools collection by instantiating it and adding to the readonly tools array.
    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),
    ];
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: the performance impact of optional parameters ('Each additional parameter significantly increases execution time'), the action type ('st.openPersonPage action'), and the progressive enhancement approach (basic info first, then optional data). It doesn't mention authentication requirements, rate limits, or error conditions, but provides substantial operational guidance.

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 sized and front-loaded: the first sentence states the core purpose, followed by performance warnings and recommendations. The warning icons and structured advice make it scannable. It could be slightly more concise by combining some performance messaging, but overall it's well-structured with each sentence adding value.

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

Completeness4/5

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

For a complex tool with 11 parameters, nested objects, and no output schema, the description provides good contextual coverage. It explains the tool's purpose, performance characteristics, and usage strategy. The main gap is the lack of output format description (what 'basic information' includes), but given the detailed parameter documentation and behavioral guidance, it's mostly complete for agent 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 schema already documents all 11 parameters thoroughly. The description adds context about the performance implications of the boolean flags and the recommendation to start with basic info only, but doesn't provide additional semantic meaning 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 fetches a person's information from LinkedIn, specifying it retrieves 'basic information' and optionally additional data like experience, education, etc. It distinguishes from siblings like 'fetch_company' or 'search_people' by focusing on individual profile retrieval rather than company data or search functionality. However, it doesn't explicitly contrast with 'nv_fetch_person' which appears to be a similar sibling tool.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use optional parameters: 'Only set additional retrieval flags to true if you specifically need that data' and 'Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task.' This gives clear criteria for parameter selection and performance optimization, though it doesn't specify when to use this tool versus alternatives like 'nv_fetch_person'.

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