Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_limited_partners_search

Search PitchBook limited partners dataset. Searches the crawled public PitchBook limited partner (institutional investor — e.g. pension fund, endowment, insurance company) profile catalog stored in a search index.

Instructions

Search PitchBook limited partners dataset. Searches the crawled public PitchBook limited partner (institutional investor — e.g. pension fund, endowment, insurance company) profile catalog stored in a search index. Discovered from PitchBook's public sitemap. Some limited partner profiles have no FAQ section -- this is normal, not a sign of missing data. Sort enum: relevance, name_asc, year_founded_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, recently_crawled_desc
run_idNoExact crawl run-id filter, 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
institution_typeNoExact institution type filter (e.g. Corporate Pension, Private Investment Fund, Endowment), max 128 characters
max_year_foundedNoMaximum founding year
min_year_foundedNoMinimum founding year

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

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well by disclosing cost behavior (1 credit per record, minimum 2 credits even for empty results, 100 for a full page) and data provenance (crawled from PitchBook's public sitemap). It also preempts a data quirk (some profiles lack an FAQ section, which is normal). Auth requirements aren't stated, but billing and provenance are valuable behavioral context.

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?

Purpose is front-loaded in the first sentence and the useful behavioral notes (FAQ quirk, billing) follow. The sort enum listing duplicates the schema and is wasted space, but otherwise the text is efficient.

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?

For a 10-parameter, no-output-schema, no-annotation tool, the description covers purpose, provenance, cost, and one data quirk. It does not describe the shape of returned profiles, and since no output schema exists, that gap leaves the agent guessing about what a result contains beyond mentions of FAQ sections.

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 10 parameters, so the baseline is 3. The description restates the sort enum, which is redundant with the schema, and doesn't clarify the filter semantics (e.g. hq_state format, institution_type values).

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 limited partners dataset) and clearly defines the entity as an institutional investor profile (pension fund, endowment, insurance company). This distinguishes it implicitly from sibling tools like datasets_pitchbook_investors_search and datasets_pitchbook_funds_search, though it doesn't name those alternatives.

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 never states when to use this search vs. the sibling facets/item tools or other PitchBook search endpoints. Usage is only implied by the tool name and general search semantics; no exclusions or conditions are given.

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