Assistant tool
supportmeet_list_my_requests
Lists the support requests you posted on SupportMeet: kind, title, status, reply counts and unread replies. Read-only, changes nothing.
Updated November 10, 2026
- Website
- SupportMeet · supportmeet.com
- Class
- Read
- Returns
requests[]: id, kind, title, status, situation, replies, new_replies, created_at, url
List the support requests you posted on SupportMeet: what kind of help, the title you gave it, its status and how many replies it has (and how many you have not read). No reply text.
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 supportmeet.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": "supportmeet_list_my_requests",
"arguments": {
"limit": 10
}
}
}Other SupportMeet tools
- supportmeet_list_my_circles my circles
- supportmeet_find_help help for a situation
What it does
supportmeet_list_my_requests returns the support requests you posted on SupportMeet. Each item gives the kind of help you asked for, the title you gave the request, its status, how many replies it has and how many of those you have not read yet. You also get the situation text, a created_at timestamp and a link to the request.
It is a read tool. Nothing changes when you call it: no request is created, edited or marked as read. Call it twice with the same arguments and you get the same list, so retries are safe.
Reply bodies are not part of the response. The counts tell you where a conversation stands. The url field is how you or the person you are helping get to the thread itself.
When an assistant should call it
Call it when someone asks what happened to a request they posted, which of their requests still need attention, or whether anyone has replied. It fits a quick status check before you draft an answer or point someone back to SupportMeet.
It also works as a sorting step. Look at new_replies to find conversations where someone is waiting on a reply, or at status to see what is still open. If the person wants to browse circles or look for practical help rather than their own posts, use supportmeet_list_my_circles or supportmeet_find_help instead.
Do not call it to read reply text. This tool will not return that.
Inputs and an example call
There is one optional input: limit, an integer from 1 to 50. It sets how many requests come back and defaults to 10. Send a small number when you only need the most recent few, and raise it when someone is reviewing a longer history.
The tool runs on the account connector at https://onelifevibe.com/mcp. It needs the person's OneLifeVibe sign-in through OAuth 2.1 with PKCE and the olv.read scope, and the person must have signed in to supportmeet.com with OneLifeVibe at least once. Its sign-in is set up for Meta Muse today (client onelifevibe-muse), and other MCP clients reach the no-account tools through the free connector.
A call looks like this: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"supportmeet_list_my_requests","arguments":{"limit":10}}}
What comes back
The response holds a requests array. Each entry has id, kind, title, status, situation, replies, new_replies, created_at and url.
replies is the total count of replies on the request. new_replies is how many of them you have not read, which is the number to lead with when someone asks if anything came in. status shows where the request stands, and created_at lets you order the list by age.
Use url to open the request and read the conversation there. Nothing in this response contains reply text.
Errors, limits and safety
not_linked means the OneLifeVibe sign-in worked, but the person has never signed in to supportmeet.com with OneLifeVibe. Ask them to do that once, then call the tool again.
On the Platform API the tool is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it. It acts on one member's own data, so that key is the wrong route. A platform key can still call the world catalogue, the tool registry, the network directory tool and the event log.
limit must sit between 1 and 50, so clamp values before you send them. Because the tool is read-only and idempotent, a failed call costs nothing to repeat.
Questions
Why does supportmeet_list_my_requests return not_linked?
The person has not signed in to supportmeet.com with OneLifeVibe yet, so there is no link between their account and SupportMeet. Have them sign in there once, then retry the call.
Can I call this tool with a platform API key?
It appears in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable because the tool works on a single member's data. Use the account connector at https://onelifevibe.com/mcp with the person's sign-in instead.
Does the response include the replies people wrote?
No. You get counts in replies and new_replies, plus the url for each request. Open that link to read the actual conversation.
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.