Edit intake settings
update_intakeChange settings on an intake that has already been sent — project name, due date, reminder cadence, quiet hours, which folder it's in, the client brief, or the client's name, phone, language, and timezone.
Use this instead of deleting and recreating the intake when a deadline moves or the chase cadence needs to change. If any of chase_schedule, chase_interval, chase_interval_unit, chase_at_time, max_reminders, respect_quiet_hours, due_date, or client.timezone is included, every pending reminder is cancelled and the schedule is re-planned from now — reminders already sent still count toward max_reminders. Raising max_reminders (or setting it to "unlimited") past the number already sent on a stalled intake reactivates it and resumes chasing.
The client's e-mail address cannot be changed here — the portal link and login are bound to it. Use manage_recipients to add, remove, or reinstate an address.
folder_id moves the intake to a different folder (an id from list_folders); set it to null to remove the intake from any folder. It never touches the chase schedule.
client_brief replaces the free-text brief shown to the client above the requested items; set it to null to clear it. Documents attached to the brief are managed via the dashboard or the REST endpoint POST /v1/intakes/:id/brief/files, not through this tool.
Fails if the intake is archived. At least one field must be given. Returns the full, updated intake object.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client | No | Client fields to change. Email cannot be changed here — use manage_recipients. | |
| due_date | No | Deadline in YYYY-MM-DD format. null clears it. | |
| folder_id | No | Move this intake to a different folder, using an id from list_folders. null removes it from any folder. | |
| intake_id | Yes | Intake ID returned by define_intake. | |
| owner_note | No | Private note, never shown to the client. null clears it. | |
| client_brief | No | Free-text brief shown to the client at the top of the portal, above the requested items — information from you to them: an offer, instructions, or context. Up to 5000 characters. null clears it. Documents attached to the brief go through the REST endpoint POST /v1/intakes/:id/brief/files (dashboard or REST — not available through this MCP tool set). | |
| project_name | No | Human-readable project name shown to the client. | |
| chase_at_time | No | Anchor reminders to this 24-hour local time in the client's timezone (e.g. "07:00"), overriding quiet hours. null clears it. | |
| max_reminders | No | Cap on reminder attempts (1-1000), or "unlimited". Raising this above the number already sent reactivates a stalled intake. | |
| chase_interval | No | How often to remind, only meaningful with chase_schedule="custom". Pair with chase_interval_unit. | |
| chase_schedule | No | Automated reminder cadence. default=T+2d,T+5d,T+9d,weekly. gentle=T+3d,T+8d,biweekly. aggressive=T+1d,T+3d,T+5d,every-other-day. custom=every chase_interval chase_interval_unit. off=no auto reminders. | |
| chase_interval_unit | No | Unit for chase_interval. | |
| respect_quiet_hours | No | Whether reminders pause outside 08:00-19:00 in the client's timezone. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||