Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_investors_search

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.

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. 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, 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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose substantive behavior: the source ('crawled public PitchBook sitemap', 'stored in a search index') and, crucially, the cost model (1 credit per record, minimum 2, empty result = 2, full page = 100). It omits auth/permission requirements and any error or rate-limit behavior beyond billing.

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?

Front-loaded with the verb and dataset, followed immediately by source and cost. Sentences are short and each carries information, with the only minor redundancy being the sort enum echo of the schema.

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 an 11-parameter search tool with no output schema and no annotations, the description covers purpose, data provenance, and billing, which is the information an agent most needs to call it correctly. It could go further by describing the shape of a returned investor record, but overall it is complete enough.

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 coverage is 100%, so all 11 parameters are already documented in the schema, establishing a baseline of 3. The description re-lists the sort enum and the q/description scope, which duplicates rather than extends schema information, adding no new parameter meaning.

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+resource ('Search PitchBook investors dataset') and clarifies the resource as the 'investor (fund manager/firm) profile catalog,' which separates it from the sibling companies/funds/advisors/limited-partners search tools. It does not explicitly name those alternatives, so it stops short of full 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 Guidelines3/5

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

Usage is implied by the word 'Search' over a described catalog, but there is no explicit when-to-use, when-not-to-use, or pointer to the sibling 'datasets_pitchbook_investors_item' / facets tools for drilling down. The billing note helps an agent decide whether to spend credits but does not guide tool selection.

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