Assistant tool
helpbless_list_my_needs
Lists the needs a person posted on HelpBLESS, with status and how much has been raised, so an assistant can answer questions about their asks.
Updated November 6, 2026
- Website
- HelpBLESS · helpbless.com
- Class
- Read
- Returns
needs[]: id, title, kind, status, raised_cents, goal_cents, currency, created_at, url
List the needs you posted on HelpBLESS with their status and how much has been raised.
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_my_needs",
"arguments": {
"limit": 10
}
}
}
Other HelpBLESS tools
- helpbless_list_my_gifts gifts I gave
- helpbless_list_saved_needs saved needs
- helpbless_save_need save or unsave a need
What it does
helpbless_list_my_needs is a read tool for HelpBLESS (helpbless.com). It lists the needs the signed-in person posted on HelpBLESS, with each need's status and how much has been raised. It changes nothing, so calling it does not create, edit, close or remove a need.
The response is a needs array. Each item carries id, title, kind, status, raised_cents, goal_cents, currency, created_at and url. Use limit to choose how many items come back: an integer from 1 to 50, default 10.
When an assistant should call it
Call it when the person asks which asks they have posted on HelpBLESS, what state those asks are in, or how much has been raised toward a goal. It fits questions about their own asks and their progress. It returns only the person's own needs.
Before this works, the person must have signed in to helpbless.com with OneLifeVibe once. If they have not, the tool answers not_linked. For related questions, use the sibling tools on the same website: helpbless_list_my_gifts for gifts, helpbless_list_saved_needs for saved needs, and helpbless_save_need to save a need.
Inputs and an example call
The only input is limit, optional. Send an integer from 1 to 50. If you omit it, the tool returns 10 items.
Use the account connector at https://onelifevibe.com/mcp. It needs the person's OneLifeVibe sign-in: OAuth 2.1 with PKCE, scope olv.read. 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.
An example call sends method tools/call with params.name helpbless_list_my_needs and params.arguments.limit set to 10. Use id 1 for the request and send it to https://onelifevibe.com/mcp. The call is read-only and idempotent, so retrying it does not change data.
What comes back
On success, the tool returns needs[]. Each entry has id, title, kind, status, raised_cents, goal_cents, currency, created_at and url. raised_cents and goal_cents are integer amounts in cents; currency tells you which currency applies. status tells you where the need stands. url is the link to the need.
Use the returned fields for display and follow-on actions. Do not calculate a different total or infer a different status from other data. If you need more items, raise limit up to 50.
Errors, limits and safety
not_linked means the person has not signed in to helpbless.com with OneLifeVibe once. Send them to helpbless.com to sign in, then retry. The tool needs an account; noAccountNeeded is false.
Through the Platform API registry, the tool appears in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today. That is 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.
limit must be an integer from 1 to 50; the default is 10. The tool is read-only, non-destructive and idempotent. It returns the member's own asks, so keep the response within that person's session and do not present it as another member's data.
Questions
What does helpbless_list_my_needs return?
It returns a needs array for the signed-in person. Each item includes id, title, kind, status, raised_cents, goal_cents, currency, created_at and url, with the amount raised toward the goal.
Why do I get not_linked from helpbless_list_my_needs?
The person has not signed in to helpbless.com with OneLifeVibe once. Have them sign in at helpbless.com, then call the tool again through the account connector.
Can a platform API key call helpbless_list_my_needs?
It is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today. The tool acts on one member's own data, so use the account connector with OAuth 2.1, PKCE and scope olv.read.
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.