Skip to main content
Glama
Cyreslab-AI

Crunchbase MCP Server

get_funding_rounds

Retrieve funding round details for a specific company using the Crunchbase MCP Server. Input a company name or ID to access funding information and limit results as needed.

Instructions

Get funding rounds for a specific company

Input Schema

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

Implementation Reference

  • MCP tool handler implementation for 'get_funding_rounds'. Validates input arguments, constructs GetFundingRoundsInput parameters, calls CrunchbaseAPI.getFundingRounds, and returns the result as JSON text content.
    case 'get_funding_rounds': {
      if (!args || typeof args !== 'object' || !('company_name_or_id' in args) || typeof args.company_name_or_id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Missing or invalid company_name_or_id parameter');
      }
      const params: GetFundingRoundsInput = {
        company_name_or_id: args.company_name_or_id,
        limit: typeof args.limit === 'number' ? args.limit : undefined
      };
      const fundingRounds = await this.crunchbaseApi.getFundingRounds(params);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(fundingRounds, null, 2),
          },
        ],
      };
    }
  • src/index.ts:243-260 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and inputSchema for 'get_funding_rounds'.
    {
      name: 'get_funding_rounds',
      description: 'Get funding rounds for 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)',
          },
        },
        required: ['company_name_or_id'],
      },
    },
  • Core helper function in CrunchbaseAPI class that implements the API call to retrieve funding rounds: first resolves company UUID, then queries Crunchbase API endpoint for funding_rounds.
    async getFundingRounds(params: GetFundingRoundsInput): Promise<FundingRound[]> {
      try {
        // First, get the company UUID
        const company = await this.getCompanyDetails({ name_or_id: params.company_name_or_id });
    
        // Then, get the funding rounds
        const response = await this.client.get<CrunchbaseApiResponse<FundingRound[]>>(`/entities/organizations/${company.uuid}/funding_rounds`, {
          params: {
            limit: params.limit || 10,
            order: 'announced_on DESC'
          }
        });
    
        return response.data.data;
      } catch (error) {
        console.error('Error getting funding rounds:', error);
        throw this.handleError(error);
      }
    }
  • TypeScript interface defining the input shape for getFundingRoundsInput used by the tool handler and API helper.
    export interface GetFundingRoundsInput {
      company_name_or_id: string;
      limit?: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe important behavioral traits like whether this is a read-only operation, what happens with invalid inputs, rate limits, authentication requirements, or what the return format looks like. The description is minimal and lacks operational context.

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 core purpose without any wasted words. It's appropriately sized for this simple tool and gets straight to the point with zero redundancy.

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?

For a tool with no annotations, no output schema, and 2 parameters, the description is insufficiently complete. It doesn't explain what format the funding rounds data will be returned in, what fields to expect, whether there's pagination, or any error conditions. The agent would need to guess about the tool's behavior and output.

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 input schema has 100% description coverage, with both parameters clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline expectation but doesn't provide extra value.

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 verb 'Get' and resource 'funding rounds for a specific company', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_company_details' which might also provide funding information, preventing 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 like 'search_companies' or 'get_company_details'. It doesn't mention prerequisites, exclusions, or comparative advantages, leaving the agent to guess about appropriate usage contexts.

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