Skip to main content
Glama

run_tracxn_investors

Retrieve a Tracxn investor profile by URL or ID token to get type, headquarters, portfolio and exit counts, top and recent investments, breakdowns, team, co-investors, and news.

Instructions

Get one investor (VC, PE, angel network, family office ...) from Tracxn by profile URL or id token: type, founding year, headquarters, portfolio and unicorn / IPO / acquisition counts, top investments, yearly / stage / sector / geography breakdowns, recent investments, team, co-investors 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": {
      "investor": "<investor>"
    },
    "name": "run_tracxn_investors"
  }
}

Input Schema

NameRequiredDescriptionDefault
investorYesInvestor URL or id token. e.g. https://tracxn.com/d/venture-capital/bessemer-venture-partners/__OeR_ESlYvM5_W8zTJB8gzBaeS0kRaT7srV12ofBbql8

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?

No annotations are provided, so the description carries the burden. It usefully discloses cost ('Flat 5 points per successful run') and enumerates the returned data (portfolio counts, breakdowns, co-investors, news), but says nothing about auth requirements, rate limits, or failure behavior.

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?

A single front-loaded sentence with the purpose first, followed by the returned fields and pricing. It is dense but every clause conveys useful scope; the long field enumeration is the only thing bordering on bloat.

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?

There is no output schema, so the description reasonably compensates by enumerating return fields (type, founding year, HQ, counts, breakdowns, team, co-investors, news). For a one-param lookup tool this is largely complete, though it omits auth and error/empty-result behavior.

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% and the single 'investor' param is fully documented in the schema, including an example URL. The description adds meaning only by noting it accepts a profile URL or id token, which the schema already states, so the baseline 3 is appropriate.

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 and resource ('Get one investor ... from Tracxn') and enumerates investor subtypes (VC, PE, angel network, family office). The provider name 'Tracxn' distinguishes it from sibling investor tools like run_pitchbook_investors and run_dealroom_investors, though it doesn't explicitly 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 Guidelines3/5

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

Usage is only implied: you use this to fetch a single investor given a URL or id token. There is no explicit statement of when to prefer this over run_tracxn_investors_search-style tools or other provider investor lookups, and no prerequisites are mentioned.

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