Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_companies_search

Search PitchBook companies dataset. Searches the crawled public PitchBook company profile catalog stored in a search index. Discovered from PitchBook's public sitemap.

Instructions

Search PitchBook companies dataset. Searches the crawled public PitchBook company profile catalog stored in a search index. Discovered from PitchBook's public sitemap. Sort enum: relevance, name_asc, year_founded_desc, investor_count_desc, recently_crawled_desc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query over name and description, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, name_asc, year_founded_desc, investor_count_desc, recently_crawled_desc
run_idNoExact crawl run-id filter, max 128 characters
statusNoExact status filter (e.g. Private, Public, Acquired, Out of Business), max 128 characters
hq_stateNoExact headquarters state/region filter, max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
hq_countryNoExact headquarters country filter, max 128 characters
financing_statusNoExact financing status filter, max 128 characters
max_year_foundedNoMaximum founding year
min_year_foundedNoMinimum founding year
ownership_statusNoExact ownership status filter, max 128 characters
primary_industryNoExact primary industry filter, max 128 characters
min_investor_countNoMinimum number of investors

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "name_asc",
+  "year_founded_desc",
+  "investor_count_desc",
+  "recently_crawled_desc"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/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, and it does disclose a critical behavioral trait: billing of 1 credit per record returned with a minimum of 2, including the edge case where an empty result still costs 2. This kind of cost disclosure is exactly what an agent needs. It does not mention rate limits, auth requirements, or pagination beyond what the schema states.

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?

Four sentences, front-loaded with the core purpose, then data provenance, sort values, and billing. Efficient and no filler, though the sort enum repetition is redundant with the schema and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter, no-required-argument search tool with 100% schema coverage and no output schema, the description covers purpose, source, and cost. It lacks guidance on the relationship to sibling item/facets tools and does not describe result shape, but the billing disclosure is the key missing piece it correctly supplies.

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 every parameter including q, sort enum, and all the exact filters is already documented in the schema. The description only repeats the sort enum values, which the schema already lists, so it adds no new parameter meaning. Baseline 3 is correct when the schema does all the parameter work.

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?

States a specific verb (Search) and resource (PitchBook companies dataset) and clarifies the data source is the crawled public PitchBook company profile catalog in a search index. It distinguishes itself from datasets_pitchbook_companies_item (which presumably fetches a single company), but does not name the sibling filters tools, leaving some differentiation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use/when-not-to-use guidance or named alternatives. The description implies this is the entry point for full-text and filter search over the companies dataset, but the agent must infer that datasets_pitchbook_companies_item handles single-record retrieval and datasets_pitchbook_companies_facets handles facet discovery.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools