Skip to main content
Each tool maps to a Partner API operation and returns its JSON as text. Lists return the compact view unless view: "full" is passed; get_* tools return the full view. Field meanings are in the API reference.

Inventory

Behaviour worth knowing

add_company accepts an optional idempotencyKey. Without one, the server derives a key from the arguments, so an identical retried call returns the first result (idempotencyReplayed: true) instead of repeating the work. Adding a company that is already tracked updates it (existingEntity: true).
thingsToTrack decides which updates trigger alerts, so the assistant must get it from the user rather than invent one. In add_company and track_lead it is optional in the schema; a call without it (or with only whitespace) tracks nothing and returns a tool error with code needs_user_input, telling the model to ask the user and call again. error.details.suggestions carries the same quick picks as the app’s add-company dialog (Product Updates, Metrics Shared, Founders Amplified, Fundraising Signals, Hiring Updates, Customer/Partnership Signals). The check runs before scopes and rate limits, so it costs no create quota. The REST API still requires thingsToTrack.
When email alerts are enabled and a rule triggers an email, add_company and track_lead use the key owner’s email as the default recipient. whoami returns it as defaultAlertEmails. Set emailAlertsEnabled: false to disable email delivery. alertEmails adds recipients, up to 20 in total. If the member has no email and none is passed, the tool returns needs_user_input for alertEmails. The REST API still requires alertEmails.
After add_company or track_lead, call get_company until operation.enrichmentComplete is true. The first run has finished when lastScrapedAt is no longer null (usually within a few minutes). lastScrapedAt, scrapeHealthReason and enrichmentStatus are present in both the compact and full views. After a successful refresh_company call, poll until lastScrapedAt differs from baselineLastScrapedAt. Manual refresh is currently enabled for Pear VC. For other workspaces, manual refresh remains paused.
list_signals and list_alerts take entityQuery, list_leads takes sourceQuery (for example "Anomaly Bio" or a founder’s name). If several companies match, the tool errors with ambiguous_entity / ambiguous_source and lists the candidates. The assistant should ask the user which one.
remove_company is annotated destructive, so compliant clients ask before running it. The server’s instructions also tell the model to confirm before removing, pausing or rejecting.
A malformed ID is rejected by the MCP layer with an input-validation error before reaching the API.

Tool errors

A failed tool call returns isError: true with the API’s error envelope as text:
The codes are those in the error reference.