Skip to main content
Glama
Meerkats-Ai

Hatch MCP Server

by Meerkats-Ai

hatch_get_linkedin_url

Find LinkedIn profiles by providing a person's name, job title, and company information to locate professional contact details.

Instructions

Find LinkedIn URL using name, designation, and company information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the person
designationNoJob title or designation of the person
companyNameYesCompany name

Implementation Reference

  • Handler logic for 'hatch_get_linkedin_url' tool: validates parameters using type guard, makes POST request to '/v1/getLinkedinUrl' API endpoint with retry logic, and returns JSON response or formatted error.
    case 'hatch_get_linkedin_url': {
      if (!isGetLinkedInUrlParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for hatch_get_linkedin_url'
        );
      }
    
      try {
        const response = await withRetry(
          async () => apiClient.post('/v1/getLinkedinUrl', args),
          'get linkedin url'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
          isError: false,
        };
      } catch (error) {
        const errorMessage = axios.isAxiosError(error)
          ? `API Error: ${error.response?.data?.message || error.message}`
          : `Error: ${error instanceof Error ? error.message : String(error)}`;
    
        return {
          content: [{ type: 'text', text: errorMessage }],
          isError: true,
        };
      }
    }
  • Tool schema definition for 'hatch_get_linkedin_url' including name, description, and input schema with properties for name, designation, and required companyName.
    const GET_LINKEDIN_URL_TOOL: Tool = {
      name: 'hatch_get_linkedin_url',
      description: 'Find LinkedIn URL using name, designation, and company information.',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the person',
          },
          designation: {
            type: 'string',
            description: 'Job title or designation of the person',
          },
          companyName: {
            type: 'string',
            description: 'Company name',
          },
        },
        required: ['companyName'],
      },
    };
  • src/index.ts:314-320 (registration)
    Registration of the 'hatch_get_linkedin_url' tool (as GET_LINKEDIN_URL_TOOL) in the listTools response.
        FIND_EMAIL_TOOL,
        FIND_PHONE_TOOL,
        VERIFY_EMAIL_TOOL,
        FIND_COMPANY_DATA_TOOL,
        GET_LINKEDIN_URL_TOOL,
      ],
    }));
  • Type guard helper function 'isGetLinkedInUrlParams' used to validate input arguments for the tool handler.
    function isGetLinkedInUrlParams(args: unknown): args is GetLinkedInUrlParams {
      if (
        typeof args !== 'object' ||
        args === null ||
        !('companyName' in args) ||
        typeof (args as { companyName: unknown }).companyName !== 'string'
      ) {
        return false;
      }
    
      // Optional parameters
      if (
        'name' in args &&
        (args as { name: unknown }).name !== undefined &&
        typeof (args as { name: unknown }).name !== 'string'
      ) {
        return false;
      }
    
      if (
        'designation' in args &&
        (args as { designation: unknown }).designation !== undefined &&
        typeof (args as { designation: unknown }).designation !== 'string'
      ) {
        return false;
      }
    
      return true;
    }
  • TypeScript interface defining the input parameters for 'hatch_get_linkedin_url' tool.
    interface GetLinkedInUrlParams {
      name?: string;
      designation?: string;
      companyName: 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 finds LinkedIn URLs but doesn't describe how it works (e.g., search method, accuracy, rate limits, authentication needs, or what happens if no match is found). This leaves significant gaps in understanding the tool's behavior and limitations.

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 uses all information effectively, making it easy to parse and understand quickly.

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 tool's complexity (finding LinkedIn URLs with three parameters) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like search methodology, error handling, or result format, leaving the agent with insufficient information for reliable use beyond basic invocation.

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?

The description adds minimal value beyond the input schema, which has 100% coverage with clear descriptions for all three parameters. It mentions the parameters (name, designation, company) but doesn't provide additional context like format examples, constraints, or how they're used in the search. With high schema coverage, the baseline score of 3 is appropriate.

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: 'Find LinkedIn URL using name, designation, and company information.' It specifies the verb ('Find'), resource ('LinkedIn URL'), and required input parameters. However, it doesn't explicitly differentiate from sibling tools like hatch_find_email or hatch_find_phone, which also find contact information but for different resources.

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 hatch_find_email or hatch_verify_email, nor does it specify prerequisites, exclusions, or contextual cues for selection. Usage is implied by the purpose but lacks explicit direction.

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/Meerkats-Ai/hatch-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server