Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_investors_search

Search a crawled catalog of PitchBook investor profiles by name, type, location, portfolio count, and exits to discover fund managers and firms.

Instructions

Search PitchBook investors dataset. Searches the crawled public PitchBook investor (fund manager/firm) profile catalog stored in a search index. Discovered from PitchBook's public sitemap. Sort enum: relevance, name_asc, portfolio_count_desc, recently_crawled_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over name and description, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, name_asc, portfolio_count_desc, recently_crawled_desc
run_idNoExact crawl run-id filter, max 128 characters
statusNoExact status filter (e.g. Active, Inactive), 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
investor_typeNoExact investor type filter (e.g. Venture Capital, Private Equity, Angel), max 128 characters
min_exits_countNoMinimum number of exits
min_portfolio_countNoMinimum current portfolio size

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",
+  "portfolio_count_desc",
+  "recently_crawled_desc"
+]
  2. Added

TDQS

B3.4/5.0
Behavior3/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 does add useful context about data provenance ('Discovered from PitchBook's public sitemap') and the sort enum. However, it does not describe default ordering, pagination constraints, result format, or how filters interact, leaving behavioral transparency partial.

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 short and front-loaded with the verb and resource, followed by useful provenance context. The sort enum list is somewhat redundant with the schema but still serves as a quick reference. There is little wasted wording, though the first and second sentences are mildly repetitive.

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

Completeness3/5

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

The schema fully documents parameters and the description clarifies the data source and search scope, making the core usage understandable. However, there is no output schema and the description does not mention what fields are returned, default pagination behavior, or how to use related facets/item tools for filtering values or full details. For an 11-parameter search tool, this is adequate but has clear 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?

Schema description coverage is 100%, so the schema already documents all 11 parameters including q, sort, page_size, and filter semantics. The description redundantly lists the sort enum but adds no meaning beyond what the schema provides. Baseline of 3 is appropriate since the schema handles parameter documentation.

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 a specific action and resource: 'Search PitchBook investors dataset' and 'Searches the crawled public PitchBook investor (fund manager/firm) profile catalog stored in a search index.' It identifies the entity type (investor/fund manager/firm), which helps distinguish it from other PitchBook dataset searches. However, it does not explicitly differentiate itself from the sibling datasets_pitchbook_investors_item or datasets_pitchbook_investors_facets tools.

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?

The description provides clear context that this is a full-text search over a crawled public profile catalog and lists sort options. However, it never states when to use this tool versus datasets_pitchbook_investors_item or datasets_pitchbook_investors_facets, and gives no exclusions or alternative routing. Usage guidance is implied but not explicit.

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