Pitch tools include field-level argument descriptions and runnable examples for MCP clients.
Tools Covered
| Tool | Mutation | Backend Routes |
|---|---|---|
pitch_get_buyer_journey |
No | /pitch-buyer-journey |
pitch_get_buyer_journey
Get buyer journey timeline for a pitch.
Backend routes: /pitch-buyer-journey
Arguments
| Field | Type | Required | Description | Example |
|---|---|---|---|---|
pitch_id |
string | Yes | Deal room / playbook pitch identifier. | PCH1774126974294428638749 |
buyer_email |
string | No | Optional buyer email to focus analytics/journey data to one contact. | buyer@acme.com |
session_id |
string | No | Optional session identifier for narrowing buyer journey results. | SES1774126974294428638749 |
page |
number | No | Pagination page number (1-based). | 1 |
limit |
number | No | Maximum records to return. | 20 |
include_internal |
boolean | No | When true, includes internal events in buyer journey timeline. | false |
include_emails |
boolean | No | When true, include email signal data in journey/analytics context. | true |
include_meetings |
boolean | No | When true, include meeting signal data in journey/analytics context. | true |
email_page_size |
number | No | Page size used for email timeline fetch in journey payload. | 200 |
viewer_id |
string | No | Optional explicit user context override. If omitted, MCP resolves this from the authenticated token/session. | IGH6969811447860000000000 |
organisation_id |
string | No | Optional explicit organisation context override. If omitted, MCP resolves this from the authenticated token/session. | PDX7478889578460000000000 |
Example Request
Fetch buyer journey scoped to contact
{
"jsonrpc": "2.0",
"id": "pitch_get_buyer_journey-1",
"method": "tools/call",
"params": {
"name": "pitch_get_buyer_journey",
"arguments": {
"pitch_id": "PCH1774126974294428638749",
"buyer_email": "buyer@acme.com",
"include_emails": true,
"include_meetings": true,
"page": 1,
"limit": 200
}
}
}
Example Success
{
"success": true,
"data": {
"tool": "pitch_get_buyer_journey",
"note": "Payload shape depends on tenant data and backend route output."
},
"error": null
}
Example Failure
{
"success": false,
"data": null,
"error": {
"code": "INVALID_ARGUMENTS",
"message": "Missing or invalid parameters for pitch_get_buyer_journey.",
"status": 400,
"retryable": false
}
}