[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)

# Set candidate status

> Change a candidate to in progress, on hold, rejected, withdrawn or hired. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/comeet/set_candidate_status

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)

Change a candidate to in progress, on hold, rejected, withdrawn or hired.

Comeet MCP tools: https://cotlet.dev/docs/mcp/comeet.md

MCP tool: `comeet_write → set_candidate_status`

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

Sets the status as the status list on the profile does. rejected and withdrawn need last_step, the last completed workflow step; for a Go/No Go or Interview step pass completed_by, the participants of that step. reason is one of your disposition reasons, and is required when your company made them required. hired needs opening, application_date and first_day. A change from in progress cancels future scheduled interviews. notify decides whether the candidate hears about a rejection: none (default), create_send_notification_step or send_message. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate from list_candidates. |
| `status` | enum | yes | in_progress, on_hold, rejected, withdrawn or hired. |
| `last_step` | string | no | Last completed step; required for rejected and withdrawn. |
| `completed_by` | array | no | Participants who completed a Go/No Go or Interview last step. |
| `reason` | string | no | Disposition reason text, e.g. Incomplete application. |
| `note` | string | no | Optional note stored with the reason. |
| `notify` | enum | no | none (default), create_send_notification_step or send_message. |
| `opening` | string | no | Opening the hire fills; required for hired. |
| `application_date` | date | no | When the hiring process began; required for hired. |
| `first_day` | date | no | First day of work; required for hired. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "comeet_write",
    "arguments": {
      "operation": "set_candidate_status",
      "arguments": {
        "candidate_id": "cand_7d21a9",
        "status": "rejected",
        "last_step": "Application review",
        "reason": "Incomplete application",
        "note": "No portfolio link in the application."
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "candidate_id": "cand_7d21a9",
    "name": "Noah Kim",
    "position": "Senior Product Designer",
    "status": "rejected",
    "last_step": "Application review",
    "reason": "Incomplete application",
    "note": "No portfolio link in the application.",
    "notified": "none",
    "cancelled_interviews": 0
  },
  "isError": false
}
```

Previous: [Comment on candidate](https://cotlet.dev/docs/mcp/comeet/add_comment.md)
Next: [Decide Go/No-go step](https://cotlet.dev/docs/mcp/comeet/decide_go_no_go.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.