Assistant tool
helpbless_list_saved_needs
Lists the HelpBLESS needs a person has saved and returns each one's id, title, kind, city, country and url. Read-only and idempotent.
Updated November 6, 2026
- Website
- HelpBLESS · helpbless.com
- Class
- Read
- Returns
needs[]: id, title, kind, city, country, url
List the needs you saved on HelpBLESS.
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.read, and the person must have signed in to helpbless.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 |
|---|---|---|
limit optional | integer 1–50 | How many items to return (default 10). |
Example request
POST https://onelifevibe.com/mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "helpbless_list_saved_needs",
"arguments": {
"limit": 10
}
}
}
Other HelpBLESS tools
- helpbless_list_my_needs my asks
- helpbless_list_my_gifts gifts I gave
- helpbless_save_need save or unsave a need
What it does
HelpBLESS (helpbless.com) is where people ask for money, time, skills or advice, and gifts go straight to a person. helpbless_list_saved_needs lists the needs one person saved there, so an assistant can refer back to them without guessing.
It sits in the Read class: it changes nothing on the account or on HelpBLESS. Calling it twice with the same limit gives the same list back, so repeating a call is safe. To add a saved need rather than read them, use helpbless_save_need. For needs the person posted, use helpbless_list_my_needs; for gifts, helpbless_list_my_gifts.
When an assistant should call it
Call it when someone asks what they saved on HelpBLESS, or when a conversation returns to a need they meant to come back to. It is also a sensible first step before suggesting a gift of time, skills or money, because a saved need already reflects what the person cared about.
Keep it out of flows where the person wants their own posted needs or their gifting history. This tool returns saved items only, and it never creates, edits or removes anything.
Inputs and an example call
There is one optional input: limit, an integer from 1 to 50, default 10. It caps how many saved needs come back.
Send a JSON-RPC 2.0 tools/call request to https://onelifevibe.com/mcp with params.name set to helpbless_list_saved_needs and params.arguments holding the limit, for example {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"helpbless_list_saved_needs","arguments":{"limit":10}}}.
Access goes through the account connector at https://onelifevibe.com/mcp. The person signs in with OneLifeVibe using OAuth 2.1 with PKCE and the scope olv.read, and must have signed in to helpbless.com with OneLifeVibe at least once. That sign-in is set up for Meta Muse today, with the client onelifevibe-muse; other MCP clients reach the no-account tools through the free connector.
What comes back
A needs array. Each entry carries id, title, kind, city, country and url. The title says what the need is, kind gives its type as HelpBLESS records it, city and country place it, and url points to the need's page on the site.
The array holds at most the number you set in limit: 10 when you leave it out, 50 at most.
Errors, limits and safety
not_linked is the error you will meet most. It means the person has not signed in to helpbless.com with OneLifeVibe yet, so the connector cannot see their saved needs. Have them sign in there once with OneLifeVibe, then retry the call.
A platform key cannot use this tool today. It is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it, 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.
Keep limit between 1 and 50. The tool is read-only, non-destructive and idempotent, so retrying after a dropped connection is safe: no call writes anything, on either side.
Questions
What does helpbless_list_saved_needs return?
A needs array where each entry has id, title, kind, city, country and url. You get at most the number you pass in limit, which defaults to 10 and cannot exceed 50.
Why does helpbless_list_saved_needs answer not_linked?
The person has not signed in to helpbless.com with OneLifeVibe yet, so no saved needs are visible to the connector. Have them sign in there once with OneLifeVibe and call the tool again.
Can a platform API key call helpbless_list_saved_needs?
No. It appears in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable because the tool acts on one member's own data. Platform keys can call the world catalogue, the tool registry, the network directory tool and the event log.
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.