Assistant tool
wuuuh_set_action_item_status
Sets the status of one of your WUUUH action-plan items to todo, doing, done or skipped. Repeat the same call and nothing further changes.
Updated November 6, 2026
- Website
- WUUUH · wuuuh.com
- Class
- Write
- Returns
id, status
Set the status of one of your WUUUH action-plan items. Repeating the same request has no further effect.
Where you can call it
- Account connector https://onelifevibe.com/mcp: needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE), scope olv.write, and the person must have signed in to wuuuh.com with OneLifeVibe once, otherwise the tool answers not_linked. Its sign-in is set up for Meta Muse today (client onelifevibe-muse); other MCP clients reach the no-account tools through the free connector.
- Platform API registry: listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today, because it acts on one member's own data; a platform key can call the world catalogue, the tool registry, the network directory tool and the event log.
Inputs
| Argument | Type | Notes |
|---|---|---|
item_id | string ≤80 | The action item id from wuuuh_list_action_plan. |
status | todo | doing | done | skipped |
Example request
POST https://onelifevibe.com/mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "wuuuh_set_action_item_status",
"arguments": {
"item_id": "<item_id from wuuuh_list…>",
"status": "todo"
}
}
}Other WUUUH tools
- wuuuh_get_dashboard my dashboard
- wuuuh_list_action_plan my action plan
What it does
wuuuh_set_action_item_status is a write tool on WUUUH (wuuuh.com), the site for people who have lost income and are working through their next best move, official links and mutual aid. It takes a single action item that belongs to the signed-in person and sets its status.
It takes two inputs: item_id, the identifier of the action item, and status, one of todo, doing, done or skipped. The call returns the id and the status now stored. The tool is idempotent, so sending the same item_id and status twice leaves the item in the same state and has no further effect. It is not destructive: it changes a status value rather than removing anything.
When an assistant should call it
Call it when the person wants to move a step in their own action plan forward or out of the way. Typical phrasing: they finished a task, they are starting one now, they want to reset something to todo, or they have decided to skip a step. Map what they say to one of the four status values and send it.
Do not guess an item id. Call wuuuh_list_action_plan first and match the item the person named against the returned list, then set the status on that id. If the person names a step loosely, confirm which item you matched before writing, since the call changes their real plan on wuuuh.com.
One call handles one item. Leave items the person did not mention untouched.
Inputs and an example call
item_id is required and is a string of up to 80 characters. Take it from wuuuh_list_action_plan rather than constructing one. status is required and must be exactly todo, doing, done or skipped; any other value is not a valid input.
Send the call to https://onelifevibe.com/mcp using the tools/call method with the tool name wuuuh_set_action_item_status and arguments holding item_id, set to the id from wuuuh_list_action_plan, and status, for example doing.
The same endpoint carries the rest of this website's tools: wuuuh_get_dashboard for an overview and wuuuh_list_action_plan for the current plan. Listing first, then writing, keeps the ids and the status values consistent.
What comes back
A successful call returns id and status. The id echoes the item you sent, and status is the value now stored for it. That is the whole result, so read those two fields and report the change to the person in their own words.
If you need to show the plan after the change, call wuuuh_list_action_plan again and read the item from that list. Do not assume other fields of the item changed; the tool sets a status.
Errors, limits and safety
The account connector needs the person's OneLifeVibe sign-in, using OAuth 2.1 with PKCE and the scope olv.write. The person must also have signed in to wuuuh.com with OneLifeVibe once. If they have not, the tool answers not_linked. Handle that by telling them to sign in to wuuuh.com with OneLifeVibe, then retry the same call. The connector's sign-in is set up for Meta Muse today (client onelifevibe-muse); other MCP clients reach the no-account tools through the free connector.
The tool appears in the platform API registry at GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today, because it acts on one member's own data. A platform key can call the world catalogue, the tool registry, the network directory tool and the event log instead.
Retries are safe: because the tool is idempotent, resending the same item_id and status after a network failure will not apply the change twice.
Questions
Why does wuuuh_set_action_item_status return not_linked?
The person has not signed in to wuuuh.com with OneLifeVibe, so the tool has no linked WUUUH account to act on. Have them complete that sign-in once, then send the same item_id and status again.
Is it safe to retry wuuuh_set_action_item_status?
Yes. The tool is idempotent, so repeating the same request has no further effect and the item stays in the status you sent. Retrying after a dropped connection or a timeout will not apply the change twice.
Can I call it with a platform API key?
Not today. The tool is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable because it acts on one member's own data. Use the account connector at https://onelifevibe.com/mcp with the person's OneLifeVibe sign-in and the olv.write scope.
Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.