Skip to main content
Glama

web_data_crunchbase_company

Extract structured company data from Crunchbase URLs to analyze business information without web scraping.

Instructions

Quickly read structured crunchbase company data This can be a cache lookup, so it can be more reliable than scraping

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • The core handler logic for the web_data_crunchbase_company tool. It triggers a BrightData dataset collection using the specific dataset_id and polls the snapshot status until data is ready or times out after 600 attempts.
    execute: tool_fn(`web_data_${id}`, async(data, ctx)=>{
        let trigger_response = await axios({
            url: 'https://api.brightdata.com/datasets/v3/trigger',
            params: {dataset_id, include_errors: true},
            method: 'POST',
            data: [data],
            headers: api_headers(),
        });
        if (!trigger_response.data?.snapshot_id)
            throw new Error('No snapshot ID returned from request');
        let snapshot_id = trigger_response.data.snapshot_id;
        console.error(`[web_data_${id}] triggered collection with `
            +`snapshot ID: ${snapshot_id}`);
        let max_attempts = 600;
        let attempts = 0;
        while (attempts < max_attempts)
        {
            try {
                if (ctx && ctx.reportProgress)
                {
                    await ctx.reportProgress({
                        progress: attempts,
                        total: max_attempts,
                        message: `Polling for data (attempt `
                            +`${attempts + 1}/${max_attempts})`,
                    });
                }
                let snapshot_response = await axios({
                    url: `https://api.brightdata.com/datasets/v3`
                        +`/snapshot/${snapshot_id}`,
                    params: {format: 'json'},
                    method: 'GET',
                    headers: api_headers(),
                });
                if (['running', 'building'].includes(snapshot_response.data?.status))
                {
                    console.error(`[web_data_${id}] snapshot not ready, `
                        +`polling again (attempt `
                        +`${attempts + 1}/${max_attempts})`);
                    attempts++;
                    await new Promise(resolve=>setTimeout(resolve, 1000));
                    continue;
                }
                console.error(`[web_data_${id}] snapshot data received `
                    +`after ${attempts + 1} attempts`);
                let result_data = JSON.stringify(snapshot_response.data);
                return result_data;
            } catch(e){
                console.error(`[web_data_${id}] polling error: `
                    +`${e.message}`);
                attempts++;
                await new Promise(resolve=>setTimeout(resolve, 1000));
            }
        }
        throw new Error(`Timeout after ${max_attempts} seconds waiting `
            +`for data`);
    }),
  • Dynamic schema construction for the tool parameters based on the inputs array from the dataset config. For crunchbase_company, inputs=['url'], so parameter 'url' is z.string().url().
    let parameters = {};
    for (let input of inputs)
    {
        let param_schema = input=='url' ? z.string().url() : z.string();
        parameters[input] = defaults[input] !== undefined ?
            param_schema.default(defaults[input]) : param_schema;
    }
  • server.js:409-416 (registration)
    Registration of the dataset configuration for crunchbase_company, which is used in the loop to create the 'web_data_crunchbase_company' tool with name `web_data_${id}`.
        id: 'crunchbase_company',
        dataset_id: 'gd_l1vijqt9jfj7olije',
        description: [
            'Quickly read structured crunchbase company data',
            'This can be a cache lookup, so it can be more reliable than scraping',
        ].join('\n'),
        inputs: ['url'],
    },
  • server.js:683-686 (registration)
    The addTool call that registers the web_data_crunchbase_company tool using the dataset config.
    addTool({
        name: `web_data_${id}`,
        description,
        parameters: z.object(parameters),
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. It mentions the tool can be a cache lookup and more reliable than scraping, which adds some context about performance and data source. However, it doesn't disclose critical behavioral traits such as whether it's read-only, potential rate limits, authentication needs, error handling, or what 'structured data' entails in terms of format. For a tool with no annotations, this leaves significant gaps.

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 brief with two sentences that are front-loaded with the main purpose. There's no unnecessary verbosity, and each sentence adds value (purpose and reliability context). However, it could be slightly more structured by explicitly separating usage notes, but overall it's efficient.

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 has no annotations, no output schema, and low parameter coverage (0%), the description is incomplete. It covers the basic purpose and a reliability note but misses key contextual details: it doesn't explain the return format (what 'structured data' means), error conditions, or how to interpret results. For a data retrieval tool with siblings offering similar functions, this lacks sufficient guidance for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter (url) with 0% description coverage, meaning the schema provides no semantic information about the parameter. The description doesn't mention the 'url' parameter at all, failing to explain what URL is expected (e.g., a Crunchbase company page URL) or any format specifics beyond the schema's URI format. With low schema coverage, the description doesn't compensate, leaving the parameter poorly documented.

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 states the tool reads structured Crunchbase company data, which is a clear verb+resource combination. However, it doesn't specifically distinguish this tool from sibling tools like 'web_data_linkedin_company_profile' or 'web_data_zoominfo_company_profile' beyond mentioning Crunchbase as the source. The purpose is understandable but lacks sibling differentiation.

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 mentions this can be a cache lookup and more reliable than scraping, which provides some implied context about when to use it (for reliability). However, it doesn't explicitly state when to use this tool versus alternatives like 'scrape_as_html' or 'scrape_as_markdown' for Crunchbase data, nor does it provide clear exclusions or prerequisites. The guidance is minimal and incomplete.

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/dsouza-anush/brightdata-mcp-heroku'

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