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

nv_fetch_person

Open a person page in Sales Navigator to retrieve their basic information using their hashed LinkedIn URL.

Instructions

Allows you to open a person page in Sales Navigator to retrieve their basic information (nv.openPersonPage action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
personHashedUrlYesHashed LinkedIn URL of the person.

Implementation Reference

  • Defines the NvFetchPersonTool class which implements the 'nv_fetch_person' MCP tool. Sets the tool name, maps to the underlying operation (OPERATION_NAME.nvFetchPerson), defines Zod input schema, and provides the MCP Tool object with inputSchema.
    export class NvFetchPersonTool extends OperationTool<TNvOpenPersonPageParams, unknown> {
      public override readonly name = 'nv_fetch_person';
      public override readonly operationName = OPERATION_NAME.nvFetchPerson;
      protected override readonly schema = z.object({
        personHashedUrl: z.string(),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to open a person page in Sales Navigator to retrieve their basic information (nv.openPersonPage action).',
          inputSchema: {
            type: 'object',
            properties: {
              personHashedUrl: {
                type: 'string',
                description: 'Hashed LinkedIn URL of the person.',
              },
            },
            required: ['personHashedUrl'],
          },
        };
      }
  • Registers the NvFetchPersonTool instance within the LinkedApiTools class constructor by adding it to the tools array.
    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 execute method in OperationTool (base class for NvFetchPersonTool) that handles the tool execution: locates the specific operation by operationName ('nvFetchPerson'), validates params, and executes it via executeWithProgress.
    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 for input validation of personHashedUrl.
    protected override readonly schema = z.object({
      personHashedUrl: z.string(),
    });
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 states the tool opens a page to retrieve information, implying a read-only operation, but doesn't specify whether this requires authentication, has rate limits, affects system state, or what the retrieval entails (e.g., format, completeness). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly, with no wasted information.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'basic information' includes, how the retrieval works, or any behavioral constraints. For a tool that interacts with an external service (Sales Navigator) and has siblings with similar names, more context is needed to ensure proper usage.

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%, with the single parameter 'personHashedUrl' well-documented in the schema. The description adds no additional parameter semantics beyond implying it's used for opening a person page, which aligns with but doesn't enhance the schema's information. Baseline 3 is appropriate as the schema handles the parameter documentation adequately.

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 action ('open a person page in Sales Navigator') and the resource ('to retrieve their basic information'), with specific reference to the 'nv.openPersonPage action'. However, it doesn't explicitly differentiate from sibling tools like 'fetch_person' or 'nv_search_people', which appear to serve related but potentially different functions.

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_person' or 'nv_search_people'. It mentions the action but gives no context about prerequisites, limitations, or comparative use cases with sibling tools, leaving the agent without clear selection criteria.

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