Skip to main content
Glama

run_pitchbook_companies

Retrieve a company's public PitchBook preview by ID or URL, including profile details, deals, competitors, investors, and related research in one structured response.

Instructions

Get the public profile preview of a company by PitchBook id or URL: description, website, founded year, status, employees, industries, parent company, address, social links, FAQs, the latest deals, competitors, investors, investments, affiliates and patent tables shown in the free preview, verticals, related research and news. Flat 5 points per successful run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "run_pitchbook_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesProfile id or PitchBook URL. e.g. 439834-78

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior: the result is a limited 'free preview' and the call costs a flat 5 points per successful run. However, it omits auth requirements, rate limits, and error behavior, leaving meaningful gaps.

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 verb and resource are front-loaded in the first clause, and the cost note is placed last where it belongs. The long field enumeration is informative but borders on verbose, costing a point.

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?

With no output schema, the description correctly compensates by enumerating the returned fields, so an agent knows what it gets back. The remaining gap is behavioral (auth, limits, preview truncation), not informational.

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% (the 'company' param already documents id or URL with an example), so the schema does the heavy lifting. The description merely restates 'by PitchBook id or URL' without adding format or validation detail, so baseline 3 applies.

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 ('Get'), resource ('public profile preview of a company'), and identifier basis ('PitchBook id or URL'). It enumerates the returned fields, making its scope clear and distinguishing it from run_pitchbook_investors, though it never names a sibling explicitly.

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 requirement of a PitchBook id or URL implies this is for fetching one known company rather than discovering companies (e.g. run_pitchbook_profiles_search), but no when-to-use guidance, prerequisites, or named alternatives are given. Usage is only faintly implied.

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