Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_advisors_search

Search public PitchBook advisor profiles to find investment banks, lenders, or financing advisory firms. Filter by service type, HQ location, and founding year.

Instructions

Search PitchBook advisors dataset. Searches the crawled public PitchBook advisor (service provider — e.g. investment bank, lender, financing advisory firm) profile catalog stored in a search index. Discovered from PitchBook's public sitemap. Sort enum: relevance, name_asc, year_founded_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, 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
service_typeNoExact service provider type filter (e.g. Commercial Bank, Investment Bank, Financing Advisory), 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.2/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It mentions the data comes from a public sitemap crawl, implying a read-only nature, but it does not explicitly state that the tool is non-destructive or describe any side effects. It also doesn't mention any limitations like pagination constraints or that results are from a snapshot, so it provides only partial transparency.

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 compact, with the core purpose stated first. It includes useful context (advisor definition, public crawl origin) without being overly verbose. Minor redundancy exists ('Search' repeated), but overall it's efficient and well-structured.

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?

Given 10 parameters and no output schema, the description is thin on what the tool returns. It doesn't mention that results are a list of advisor profiles or how pagination works, though these are in the schema. It also doesn't highlight the filtering capabilities (e.g., by HQ country, service type), which are central to using the tool effectively. The description is adequate but leaves the agent to rely heavily on the schema.

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 baseline is 3. The description adds context about the dataset's origin but does not add meaning to individual parameters beyond what the schema already says. It lists the sort enum values, but those are also in the schema. No extra semantic value is provided for parameters like q, page_size, or filters.

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 the tool searches the PitchBook advisors dataset, specifying the resource (crawled public advisor profile catalog) and the general purpose (search). It also clarifies what advisors are (service providers like investment banks, lenders). However, it does not explicitly differentiate from related siblings like datasets_pitchbook_advisors_item or datasets_pitchbook_advisors_facets, so it's clear but slightly lacking in sibling distinction.

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?

There is no guidance on when to use this search tool versus alternatives such as the item detail or facets tools. No conditions, exclusions, or context for selecting this tool over siblings are provided. The description only explains what the tool does, not when to favor it, so it leaves the agent to infer usage.

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