[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Update opportunity

> Move an opportunity to another stage or set its status, loss reason and close date. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/copper-crm/update_opportunity

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Move an opportunity to another stage or set its status, loss reason and close date.

Copper CRM MCP tools: https://cotlet.dev/docs/mcp/copper-crm.md

MCP tool: `copper_crm_write → update_opportunity`

Access: write. Confirm: waits for the user's OK before it runs.

Changes only the fields you pass. Set status to Won, Lost, Abandoned or Open. For Lost, pass loss_reason from list_pipelines, as the Loss Reasons box in Copper asks for one, and set close_date to today to keep reports accurate. Other users see the change, and Workflow Automation rules may fire on it. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `opportunity_id` | string | yes | Id from list_opportunities. |
| `stage` | string | no | Stage name within the opportunity's pipeline. |
| `status` | enum | no | Open, Won, Lost or Abandoned. |
| `loss_reason` | string | no | Loss reason name from list_pipelines. Used with status Lost. |
| `close_date` | date | no | Close date, YYYY-MM-DD. |
| `monetary_value` | number | no | Value of the opportunity. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "copper_crm_write",
    "arguments": {
      "operation": "update_opportunity",
      "arguments": {
        "opportunity_id": "31842907",
        "status": "Lost",
        "loss_reason": "Price",
        "close_date": "2026-10-20"
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "opportunity_id": "31842907",
    "name": "Northwind renewal",
    "pipeline": "Sales",
    "stage": "Negotiation",
    "status": "Lost",
    "loss_reason": "Price",
    "close_date": "2026-10-20",
    "monetary_value": 18000
  },
  "isError": false
}
```

Previous: [Create opportunity](https://cotlet.dev/docs/mcp/copper-crm/create_opportunity.md)
Next: [Create task](https://cotlet.dev/docs/mcp/copper-crm/create_task.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.