Skip to main content
Glama
Cyreslab-AI

Crunchbase MCP Server

search_companies

Find companies using filters like category, location, founding date, and status. Retrieve detailed results from Crunchbase data for efficient research and analysis.

Instructions

Search for companies based on various criteria

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (e.g., "Artificial Intelligence", "Fintech")
founded_afterNoFilter by founding date (YYYY-MM-DD)
founded_beforeNoFilter by founding date (YYYY-MM-DD)
limitNoMaximum number of results to return (default: 10)
locationNoFilter by location (e.g., "San Francisco", "New York")
queryNoSearch query (e.g., company name, description)
statusNoFilter by company status (e.g., "active", "closed")

Implementation Reference

  • The MCP tool handler for 'search_companies' that processes input parameters into SearchCompaniesInput, calls the Crunchbase API wrapper, and returns the results as JSON text.
    case 'search_companies': {
      if (!args || typeof args !== 'object') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid parameters');
      }
      const params: SearchCompaniesInput = {
        query: typeof args.query === 'string' ? args.query : undefined,
        location: typeof args.location === 'string' ? args.location : undefined,
        category: typeof args.category === 'string' ? args.category : undefined,
        founded_after: typeof args.founded_after === 'string' ? args.founded_after : undefined,
        founded_before: typeof args.founded_before === 'string' ? args.founded_before : undefined,
        status: typeof args.status === 'string' ? args.status : undefined,
        limit: typeof args.limit === 'number' ? args.limit : undefined
      };
      const companies = await this.crunchbaseApi.searchCompanies(params);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(companies, null, 2),
          },
        ],
      };
    }
  • src/index.ts:192-228 (registration)
    Registration of the 'search_companies' tool in the listTools response, defining its name, description, and input schema matching SearchCompaniesInput.
    {
      name: 'search_companies',
      description: 'Search for companies based on various criteria',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query (e.g., company name, description)',
          },
          location: {
            type: 'string',
            description: 'Filter by location (e.g., "San Francisco", "New York")',
          },
          category: {
            type: 'string',
            description: 'Filter by category (e.g., "Artificial Intelligence", "Fintech")',
          },
          founded_after: {
            type: 'string',
            description: 'Filter by founding date (YYYY-MM-DD)',
          },
          founded_before: {
            type: 'string',
            description: 'Filter by founding date (YYYY-MM-DD)',
          },
          status: {
            type: 'string',
            description: 'Filter by company status (e.g., "active", "closed")',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 10)',
          },
        },
      },
    },
  • TypeScript interface SearchCompaniesInput defining the input parameters for the search_companies tool and API method.
    export interface SearchCompaniesInput {
      query?: string;
      location?: string;
      category?: string;
      founded_after?: string;
      founded_before?: string;
      status?: string;
      limit?: number;
    }
  • Helper method in CrunchbaseAPI class that builds the search query from parameters and performs the HTTP request to Crunchbase API's /searches/organizations endpoint.
    async searchCompanies(params: SearchCompaniesInput): Promise<Company[]> {
      try {
        // Build the query string based on the provided parameters
        let query = params.query || '';
    
        if (params.location) {
          query += ` AND location:${params.location}`;
        }
    
        if (params.category) {
          query += ` AND category:${params.category}`;
        }
    
        if (params.founded_after) {
          query += ` AND founded_on:>=${params.founded_after}`;
        }
    
        if (params.founded_before) {
          query += ` AND founded_on:<=${params.founded_before}`;
        }
    
        if (params.status) {
          query += ` AND status:${params.status}`;
        }
    
        const response = await this.client.get<CrunchbaseApiResponse<Company[]>>('/searches/organizations', {
          params: {
            query,
            limit: params.limit || 10,
            order: 'rank DESC'
          }
        });
    
        return response.data.data;
      } catch (error) {
        console.error('Error searching companies:', error);
        throw this.handleError(error);
      }
    }
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 but offers minimal insight. It states the tool searches but doesn't describe return format (e.g., list of companies with what fields), pagination behavior (implied by 'limit' parameter), error conditions, or performance characteristics. For a search tool with 7 parameters, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource. However, it could be more structured by explicitly listing key criteria or mentioning output expectations to improve usability without sacrificing brevity.

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 complexity (7 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what the search returns (e.g., company names, IDs, summaries), how results are ordered, or handle cases like no matches. For a search tool with multiple filters, more context is needed to guide effective use, especially without annotations or output schema to fill gaps.

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 mentions 'various criteria,' which loosely maps to the 7 parameters in the schema. However, with 100% schema description coverage, the schema already fully documents each parameter's purpose and format. The description adds no specific meaning beyond what's in the schema, such as explaining how parameters interact or providing examples beyond the schema's hints. 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search for companies based on various criteria' clearly states the action (search) and resource (companies), making the purpose understandable. However, it's vague about what 'various criteria' entails and doesn't differentiate from sibling tools like 'search_people' beyond the resource type. It's adequate but lacks specificity about scope or how it differs from other company-related tools.

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 relationships with sibling tools like 'get_company_details' (for specific company info) or 'search_people' (for searching individuals), nor does it specify prerequisites or contexts for use. The agent must infer usage from the tool name alone.

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

Related 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/Cyreslab-AI/crunchbase-mcp-server'

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