Skip to main content
Glama
freesolo-co

Clado MCP Server

by freesolo-co

search_for_users

Find LinkedIn users by applying filters such as school, company, or natural language queries to locate specific professional profiles.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query to find LinkedIn profiles
limitNoMaximum number of profiles to return (1–100)
schoolsNoList of school names to filter results by, e.g., ['Stanford', 'MIT']
companiesNoList of company names to filter results by
advanced_filteringNoEnable AI agent-based filtering to improve result quality
search_idNoID from previous search for pagination
offsetNoNumber of results to skip for pagination

Implementation Reference

  • Implementation of the search_for_users tool handler function that constructs a URL with parameters and makes an API request to Clado's search endpoint.
    export const searchForUsersTool = async ({
      query,
      limit = 30,
      schools,
      companies,
      advanced_filtering = true,
      search_id,
      offset = 0,
    }: SearchForUsersParams) => {
    
      const url = new URL("https://search.clado.ai/api/search");
      url.searchParams.append("query", query);
      url.searchParams.append("limit", String(Math.min(limit, 100)));
      url.searchParams.append("advanced_filtering", String(advanced_filtering));
      
      if (offset > 0) {
        url.searchParams.append("offset", String(offset));
      }
      
      if (search_id) {
        url.searchParams.append("search_id", search_id);
      }
    
      if (schools && schools.length > 0) {
        schools.forEach((s: string) => url.searchParams.append("schools", s));
      }
      
      if (companies && companies.length > 0) {
        companies.forEach((c: string) => url.searchParams.append("companies", c));
      }
    
      const response = await makeCladoRequest(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 successfully: ${JSON.stringify(responseData, null, 2)}`
          }
        ]
      };
    };
  • Zod schema defining the input parameters for the search_for_users tool.
    export const searchForUsersSchema = {
      query: z.string().describe("Natural language search query to find LinkedIn profiles"),
      limit: z.number().min(1).max(100).default(30).describe("Maximum number of profiles to return (1–100)"),
      schools: z.array(z.string()).optional().describe("List of school names to filter results by, e.g., ['Stanford', 'MIT']"),
      companies: z.array(z.string()).optional().describe("List of company names to filter results by"),
      advanced_filtering: z
        .boolean()
        .default(true)
        .describe("Enable AI agent-based filtering to improve result quality"),
      search_id: z.string().uuid().optional().describe("ID from previous search for pagination"),
      offset: z.number().min(0).default(0).optional().describe("Number of results to skip for pagination"),
    };
  • src/index.ts:24-28 (registration)
    Registration of the search_for_users tool on the MCP server in the main entry point.
    server.tool(
      searchForUsersName,
      searchForUsersDescription,
      searchForUsersSchema,
      searchForUsersTool
  • Registration of the search_for_users tool on the MCP server in the setup function.
    searchForUsersName,
    searchForUsersDescription,
    searchForUsersSchema,
    searchForUsersTool
  • Name and description exports used for tool registration.
    export const searchForUsersName = "search_for_users";
    
    export const searchForUsersDescription = "Search for users on Clado using filters like query, school, and match threshold.";
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'filters like query, school, and match threshold' but doesn't disclose critical traits: whether this is a read-only operation, rate limits, authentication needs, result format, or what 'match threshold' entails. For a search tool with 7 parameters, this is inadequate.

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 with zero waste. It's front-loaded with the core purpose and includes specific examples of filters. Every word earns its place, making it easy to parse 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 (7 parameters, no annotations, no output schema), the description is insufficient. It lacks details on behavioral traits, result format, pagination behavior (implied by 'search_id' and 'offset' but not explained), and differentiation from siblings. For a search tool with multiple filters, more context is needed to guide effective 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 fully documents all 7 parameters. The description adds marginal value by highlighting 'query, school, and match threshold' as key filters, but 'match threshold' isn't in the schema, creating confusion. Baseline 3 is appropriate as the schema does heavy lifting, though the description's mention of an undefined parameter slightly detracts.

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 Clado'), with specific filters mentioned. It distinguishes from siblings by focusing on user search rather than enrichment, posting, or scraping. However, it doesn't explicitly differentiate from 'retrieve_contacts' which might overlap in retrieving user information.

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?

No guidance is provided on when to use this tool versus alternatives like 'enrich_linkedin' or 'retrieve_contacts'. The description mentions filters but doesn't specify use cases, prerequisites, or exclusions. This leaves the agent without context for tool selection among siblings.

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/freesolo-co/mcp'

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