---
name: privsource-pending-deals
description: Use when an agent submits a new seller deal to PrivSource for admin review through MCP, checks its review status, edits it, or returns a dashboard deletion link.
---

# PrivSource Pending Deals

Pending deal tools are seller-side. `create_pending_deal` submits a deal to the PrivSource review queue — it creates a pending-deal resource, not a live deal. The PrivSource team reviews submissions, typically within 48 hours; approved deals become live deals visible to the buyer network and mandate matching.

## Workflow

1. Call `privsource_whoami` if unsure whether the account has `pending-deals` access.
2. Gather the deal details from whatever the seller has — a teaser PDF, a CIM, or a plain description. Extract structured fields yourself; there is no server-side document parsing on this path.
3. Only `name`, `description`, and `deal_type` are required, but include every field you can. `revenue` and `ebitda` (whole US dollars, integers) drive buyer search filters and mandate matching; `industry` and `location` drive buyer filtering. Deals with complete data get materially more buyer attention.
4. `location` and `industry` are enums — choose the closest match from the schema options rather than inventing values. Omit `location` only when the seller wants it undisclosed to buyers. `sub_industry` must belong to the chosen primary industry (the valid pairings are listed in the schema description), and `secondary_industry` must differ from `industry`.
5. Show the seller exactly what will be submitted and get their confirmation first. Submission is not idempotent — each call creates a new pending deal, and it cannot be unsubmitted through MCP.
6. Call `create_pending_deal` once. Keep the returned `id`.
7. Call `get_pending_deal` with that `id` to check status: `under review`, `approved`, or `rejected`. Once approved, the response is a minimal stub whose `deal` field carries the live deal's `id` and link — from there the seller-mandate-matches tools apply.

## Edit a pending submission

Call `update_pending_deal` with the pending `id` and the fields to change.
Omitted fields keep their values. The tool does not submit a draft or restart review.
Use the same field names and taxonomy as `create_pending_deal`.
Use an empty location string to select Undisclosed. Omit location to keep its value.
Use an empty string to clear an industry field. Keep the remaining industry fields valid together.
Approval processing and approved submissions are locked. Use `update_seller_deal` after approval.

## Delete through the dashboard

Call `get_pending_deal_deletion_link` with the pending `id`.
Return `next_action.url` to the seller. The tool does not delete anything.
The seller must open the edit page, select Delete, and confirm.
Canceling the prompt keeps the record. Confirmation soft deletes it.
Locked or deleted submissions cannot use this handoff.

## Error Handling

- "Missing required fields" or "must be one of" errors name the field and the accepted values — fix the arguments and resubmit; nothing was created.
- "Pending deal not found" means the id does not belong to this seller account or the submission was deleted from the dashboard.
- `teaser_url` and `nda_url` must be HTTPS URLs. If the seller only has a local file, submit without it and note that the teaser can be uploaded from the seller dashboard.