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

fetch_person

Retrieve a LinkedIn person's basic profile information. Optionally fetch experience, education, skills, languages, posts, comments, or reactions. Request only essential data to optimize performance.

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.
commentsRetrievalConfigNoOptional. Configuration for retrieving comments. Available only if retrieveComments is true.
reactionsRetrievalConfigNoOptional. Configuration for retrieving reactions. Available only if retrieveReactions is true.

Implementation Reference

  • The FetchPersonTool class defines the 'fetch_person' tool. It extends OperationTool which handles execution via linkedapi operations. The schema defines input params (personUrl required, optional retrieve flags for experience/education/skills/languages/posts/comments/reactions with configs). The getTool() returns the MCP Tool definition with name and inputSchema.
    export class FetchPersonTool extends OperationTool<TFetchPersonParams, unknown> {
      public override readonly name = 'fetch_person';
      public override readonly operationName = OPERATION_NAME.fetchPerson;
      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(),
        commentsRetrievalConfig: z
          .object({
            limit: z.number().min(1).max(20).optional(),
            since: z.string().optional(),
          })
          .optional(),
        reactionsRetrievalConfig: z
          .object({
            limit: z.number().min(1).max(20).optional(),
            since: z.string().optional(),
          })
          .optional(),
      });
    
      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.',
                  },
                },
              },
              commentsRetrievalConfig: {
                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.',
                  },
                },
              },
              reactionsRetrievalConfig: {
                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'],
          },
        };
      }
    }
  • Zod schema defining input validation for fetch_person. personUrl is required; optional boolean flags control retrieval of experience, education, skills, languages, posts, comments, reactions (default false). Posts/comments/reactions have optional config objects with limit (1-20) and since (ISO 8601 string).
    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(),
      commentsRetrievalConfig: z
        .object({
          limit: z.number().min(1).max(20).optional(),
          since: z.string().optional(),
        })
        .optional(),
      reactionsRetrievalConfig: z
        .object({
          limit: z.number().min(1).max(20).optional(),
          since: z.string().optional(),
        })
        .optional(),
    });
  • FetchPersonTool is instantiated and registered in the LinkedApiTools constructor's tools array, making it available alongside all other MCP 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),
    ];
  • OperationTool is the base class that FetchPersonTool extends. It provides the execute() method which finds the matching LinkedApi operation by operationName (OPERATION_NAME.fetchPerson) and runs it with progress tracking 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,
        });
      }
    }
  • LinkedApiMCPServer.getTools() maps all tools (including FetchPersonTool) to MCP Tool definitions by calling getTool(), and returns them for the ListTools request handler.
    public getTools(): Tool[] {
      const linkedApiTools = this.tools.tools.map((tool) => tool.getTool());
      const adminTools = this.tools.adminTools.map((tool) => tool.getTool());
      return [...linkedApiTools, ...adminTools];
    }
Behavior3/5

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

With no annotations, the description bears full burden for behavioral disclosure. It reveals that the tool executes an 'st.openPersonPage action' and warns about performance costs of extra parameters. However, it does not mention whether the tool is read-only, authentication requirements, or rate limits, leaving gaps in transparency.

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 concise and well-structured, front-loading the purpose and listing optional data types. The performance warning is clearly separated using emojis and bold text. It wastes no words, but could be slightly more streamlined by merging some phrases.

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?

Given the tool's complexity (11 parameters, nested objects, no output schema), the description covers the main purpose and performance considerations but does not describe the output structure or 'basic information' contents. The nested configuration parameters are left to the schema, making the description adequate but not fully complete.

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 baseline is 3. The description adds value by warning about performance impact of setting additional retrieval flags, which goes beyond the schema's descriptions. However, it does not explain parameter formats or constraints beyond what the schema already provides.

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's purpose: opening a person page to retrieve basic information and optionally additional data like experience, education, skills, etc. The verb 'fetch' and resource 'person' are explicit, and the description distinguishes it from sibling tools like fetch_company by specifying the person context.

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

Usage Guidelines3/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 additional retrieval flags with a performance warning and recommendation to start with basic info. However, it does not compare this tool to alternative sibling tools (e.g., nv_fetch_person, search_people) to help the agent decide when to use fetch_person over others.

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