Skip to main content
Glama

Pipeline CRM MCP by usefulapi

Update deal

pipelinecrm_update_deal
DestructiveIdempotent

WRITE: change fields of a deal; only the fields you pass change. Move it to another stage with stage_id. Setting probability to 100 or 0 closes the deal as won or lost; give won/loss reason ids when you do. Archive with archived: true. No email is sent to a new owner. PUT /deals/{id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew deal name.
valueNoNew value.
deal_idYesPipeline CRM deal id.
summaryNoNew description.
tag_idsNoFull list of deal tag ids (replaces the list).
archivedNotrue archives the deal, false restores it.
owner_idNoNew owner user id.
stage_idNoMove the deal to this deal stage id.
status_idNoDeal status id.
company_idNoCompany id.
person_idsNoFull list of associated person ids (replaces the list).
closed_timeNoActual close date (yyyy-mm-dd).
probabilityNoProbability of closing, 0-100. 100 closes the deal as won, 0 as lost.
custom_fieldsNoCustom field values keyed by the custom field's key (see the account's custom field labels in Pipeline CRM).
won_reason_idNoDeal won reason id.
loss_reason_idNoDeal loss reason id.
won_reason_notesNoWhy the deal was won.
loss_reason_notesNoWhy the deal was lost.
primary_contact_idNoPrimary contact person id.
expected_close_dateNoNew expected close date (yyyy-mm-dd).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.