Skip to main content
These tools run the reviewable Pitch Audit lifecycle from an MCP client: create the audit, review the prompts, then confirm to start answer collection, which uses credits. Read MCP write access first. Examples use synthetic data.
The Pitch Audit write tools require an agency team on an active Business, Agency Business or Enterprise plan. All three require the write:pitch-audits scope and the Manager role. Reading audits with list_pitch_audits and get_pitch_audit uses the separate read:pitch-audits scope.

create_pitch_audit

Create a Pitch Audit for a prospect. By default, prompts are prepared for review before any credit is used and the call needs no confirmation. When autoStartResponses is true, answer collection starts at once and uses credits, so the call needs a confirmation token.

Parameters

Example


save_pitch_audit_prompts

Replace the prompts of a Pitch Audit that is awaiting review. Every call needs a confirmation token from a preview, because it replaces the saved prompts.

Parameters

The call replaces the whole prompt set. Send every prompt you want to keep.

Example


confirm_pitch_audit

Confirm the prompts and start collecting answers. This uses the credits shown in the preview, so every execution needs a confirmation token.

Parameters

Example

Retrying a failed audit and exporting a report remain dashboard actions.