Skip to main content
Glama
Cyreslab-AI

Crunchbase MCP Server

get_acquisitions

Retrieve acquisition data for a specific company from Crunchbase. Input a company name or UUID and set a result limit to get details on acquisitions made by or of the company.

Instructions

Get acquisitions made by or of a specific company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_name_or_idNoCompany name or UUID
limitNoMaximum number of results to return (default: 10)

Implementation Reference

  • MCP tool handler for 'get_acquisitions': validates input arguments, constructs params, calls crunchbaseApi.getAcquisitions, and returns JSON stringified response.
    case 'get_acquisitions': {
      if (!args || typeof args !== 'object') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid parameters');
      }
      const params: GetAcquisitionsInput = {
        company_name_or_id: typeof args.company_name_or_id === 'string' ? args.company_name_or_id : undefined,
        limit: typeof args.limit === 'number' ? args.limit : undefined
      };
      const acquisitions = await this.crunchbaseApi.getAcquisitions(params);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(acquisitions, null, 2),
          },
        ],
      };
    }
  • Core implementation of getAcquisitions: resolves company UUID if needed, builds search query for acquisitions where the company is acquirer or acquiree, calls Crunchbase API /searches/acquisitions, returns results.
    async getAcquisitions(params: GetAcquisitionsInput): Promise<Acquisition[]> {
      try {
        let companyId: string | undefined;
    
        if (params.company_name_or_id) {
          // Get the company UUID
          const company = await this.getCompanyDetails({ name_or_id: params.company_name_or_id });
          companyId = company.uuid;
        }
    
        // Build the query
        let query = '';
        if (companyId) {
          query = `acquirer_identifier.uuid:${companyId} OR acquiree_identifier.uuid:${companyId}`;
        }
    
        // Get the acquisitions
        const response = await this.client.get<CrunchbaseApiResponse<Acquisition[]>>('/searches/acquisitions', {
          params: {
            query,
            limit: params.limit || 10,
            order: 'announced_on DESC'
          }
        });
    
        return response.data.data;
      } catch (error) {
        console.error('Error getting acquisitions:', error);
        throw this.handleError(error);
      }
  • src/index.ts:261-277 (registration)
    Tool registration in ListTools response: defines name 'get_acquisitions', description, and inputSchema.
    {
      name: 'get_acquisitions',
      description: 'Get acquisitions made by or of a specific company',
      inputSchema: {
        type: 'object',
        properties: {
          company_name_or_id: {
            type: 'string',
            description: 'Company name or UUID',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 10)',
          },
        },
      },
    },
  • TypeScript interface defining input parameters for getAcquisitions tool.
    export interface GetAcquisitionsInput {
      company_name_or_id?: string;
      limit?: number;
    }
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. While 'Get' implies a read operation, the description lacks details on permissions, rate limits, pagination, error handling, or what the return format looks like. It doesn't disclose whether this is a safe operation or has any side effects.

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 states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place.

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 for a tool with two parameters. It lacks information on behavioral traits, return values, error conditions, and usage context, which are critical for an AI agent to invoke this tool correctly without structured guidance.

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 already documents both parameters ('company_name_or_id' and 'limit') adequately. The description adds no additional parameter semantics beyond what's in the schema, such as format examples, constraints, or usage tips, meeting 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 tool's purpose with a specific verb ('Get') and resource ('acquisitions'), specifying the scope as 'made by or of a specific company'. It distinguishes from sibling tools like 'get_company_details' or 'get_funding_rounds' by focusing on acquisitions, but doesn't explicitly differentiate in the description text.

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 'search_companies' or 'search_people', nor does it specify prerequisites, exclusions, or contextual triggers for usage.

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