Skip to main content
Glama
automcp-app

Linkd MCP Server

by automcp-app

search_for_users

Find LinkedIn users by search query with filters for school names and match score thresholds to identify relevant professional connections.

Instructions

Search for users on Linkd using filters like query, school, and match threshold.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query, e.g., 'People working on AI at FAANG'
limitNoMaximum number of results to return (1–30)
schoolNoFilter by school name(s), e.g., ['Stanford', 'MIT']
acceptance_thresholdNoMatch score threshold between 0 and 100

Implementation Reference

  • The async handler function `searchForUsersTool` that implements the core logic: builds search URL with params, calls Linkd API via `makeLinkdRequest`, handles errors, and formats response as MCP content.
    export const searchForUsersTool = async ({
      query,
      limit = 10,
      school,
      acceptance_threshold = 60,
    }: SearchForUsersParams) => {
    
      const url = new URL("https://search.linkd.inc/api/search/users");
      url.searchParams.append("query", query);
      url.searchParams.append("limit", String(Math.min(limit, 30)));
      url.searchParams.append("acceptance_threshold", String(Math.max(0, Math.min(100, acceptance_threshold))));
    
      if (school && school.length > 0) {
        school.forEach((s: string) => url.searchParams.append("school", s));
      }
    
      const response = await makeLinkdRequest(url.toString(), {});
      const responseData = await response.json();
    
      if (responseData.error) {
        throw new Error(
          `Failed to search for users: ${JSON.stringify(responseData.error)}`
        );
      }
    
      return {
        content: [
          {
            type: "text" as const,
            text: `search completed succesfully: ${JSON.stringify(responseData, null, 2)}`
          }
        ]
      };
    };
  • Zod schema defining input parameters for the tool: query (string), limit (number 1-30), optional school array, acceptance_threshold (0-100).
    export const searchForUsersSchema = {
      query: z.string().describe("The search query, e.g., 'People working on AI at FAANG'"),
      limit: z.number().min(1).max(30).default(10).describe("Maximum number of results to return (1–30)"),
      school: z.array(z.string()).optional().describe("Filter by school name(s), e.g., ['Stanford', 'MIT']"),
      acceptance_threshold: z
        .number()
        .min(0)
        .max(100)
        .default(60)
        .describe("Match score threshold between 0 and 100"),
    };
  • Registers the tool on the MCP server by calling `server.tool` with name, description, schema, and handler function.
      searchForUsersName,
      searchForUsersDescription,
      searchForUsersSchema,
      searchForUsersTool
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Search for users' but doesn't clarify if this is a read-only operation, requires authentication, has rate limits, or describes the return format. The lack of such details is a significant gap for a search tool.

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 and key filters. It's front-loaded with essential information and contains no unnecessary words, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It doesn't explain behavioral traits, return values, or usage context, which are crucial for a search tool with multiple parameters. The high schema coverage doesn't compensate for these missing elements.

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 fully documents all parameters. The description adds minimal value by listing filters like query, school, and match threshold, but doesn't provide additional syntax or usage context beyond the schema. 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 action ('Search for users') and resource ('on Linkd'), specifying the tool's purpose. It mentions filters like query, school, and match threshold, which adds detail. However, it doesn't explicitly differentiate from sibling tools like 'search_for_companies' or 'retrieve_contacts', keeping it from a perfect score.

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 scenarios for usage, prerequisites, or exclusions, nor does it reference sibling tools. This leaves the agent without context for tool selection.

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/automcp-app/linkd-mcp'

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