onelifevibe

Assistant tool

helpbless_list_my_gifts

Lists the gifts a person has given on HelpBLESS, including recurring gifts, so an assistant can show giving history with amounts, currency and dates.

Updated November 6, 2026

Website
HelpBLESS · helpbless.com
Class
Read
Returns
gifts[]: need_title, amount_cents, currency, given_at, recurring

List the gifts you gave on HelpBLESS, including recurring gifts.

Where you can call it

Inputs

ArgumentTypeNotes
limit optionalinteger 1–50How 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_gifts",
    "arguments": {
      "limit": 10
    }
  }
}

Other HelpBLESS tools

What it does

helpbless_list_my_gifts is a read tool on the OneLifeVibe assistant connector. It returns the gifts one person has given on HelpBLESS, the OneLifeVibe website where people ask for money, time, skills or advice and gifts go straight to a person. Each entry in the response describes the need that was met, the amount, the currency, when the gift was given and whether it recurs.

Read means it changes nothing. The tool is idempotent, so calling it twice with the same arguments returns the same list and has no side effects on the account. Nothing is created, edited or sent when you call it.

The other HelpBLESS tools on the connector are helpbless_list_my_needs, helpbless_list_saved_needs and helpbless_save_need. Use those when the question is about the person's own requests rather than their giving.

When an assistant should call it

Call it when a person asks what they have given, how much they gave over a period, or which of their gifts are recurring. It is also the right call before a conversation about giving again, because the answer shows what the person already supports and whether a past gift repeats.

Call it only on behalf of a signed-in member. The tool reads one person's own giving history, so it needs that person's OneLifeVibe sign-in and the olv.read scope. A platform key cannot substitute for this, because the tool acts on one member's own data.

Do not use it to browse what people are asking for on HelpBLESS. It answers a question about one member's past giving, not about the site's open needs.

Inputs and an example call

There is one optional input. limit is an integer from 1 to 50 and sets how many items come back; leave it out and you get 10. For a short summary, a small limit is enough. For a full history review, raise it, but stay inside the 1 to 50 range.

Send a tools/call request to https://onelifevibe.com/mcp: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"helpbless_list_my_gifts","arguments":{"limit":10}}}

The connector uses OAuth 2.1 with PKCE and the olv.read scope, and the person must have signed in to helpbless.com with OneLifeVibe once. Meta Muse is set up today with the onelifevibe-muse client; other MCP clients reach the no-account tools through the free connector.

What comes back

The result holds a gifts array. Each item carries need_title, amount_cents, currency, given_at, recurring. need_title names the need the gift went to, and given_at is the date of the gift.

Read amount_cents together with currency rather than assuming a single currency across the list. recurring marks gifts that repeat, so a person asking about ongoing support can be answered from the same call.

If the array comes back shorter than the limit you sent, that is the whole history the person has on HelpBLESS, not an error. Raise limit only when you need more entries in one response.

Errors, limits and safety

The tool answers not_linked when the person has not signed in to helpbless.com with OneLifeVibe at least once. The fix is on their side: complete that sign-in, then call again. The tool stays read-only throughout, so a failed call leaves nothing behind.

On the Platform API, helpbless_list_my_gifts appears 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. Use the account connector at https://onelifevibe.com/mcp instead. A platform key can still call the world catalogue, the tool registry, the network directory tool and the event log.

Keep limit between 1 and 50 and expect 10 when you omit it. Retries are safe at any point because the tool is idempotent. When a call fails, read the error before changing anything: not_linked is about the person's sign-in, while 501 world_tools_unavailable is about which credential and endpoint you used.

Questions

Why does helpbless_list_my_gifts return not_linked?

The person has not signed in to helpbless.com with OneLifeVibe yet, so their giving history is not reachable through the connector. Ask them to complete that sign-in once, then call the tool again with the olv.read scope.

Can I call helpbless_list_my_gifts with a platform API key?

No. The tool is 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. Use the account connector at https://onelifevibe.com/mcp with the person's sign-in.

Does the list include recurring gifts, and how many items come back?

Yes. Every item has a recurring field, so repeating gifts appear alongside one-off ones. The optional limit input accepts 1 to 50 and defaults to 10 when you leave it out.

Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.

Get a free key Connector guide

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.