Workspace
list_profiles
List profiles. Profiles keep each of your customers' accounts apart in one workspace. Pass externalId (your own id for the customer) to find theirs, then pass its id as profileId to list_accounts, connect_account and schedule_post.
TL;DR
| Question | Answer |
|---|---|
| What does it do? | Profiles keep each of your customers' accounts apart in one workspace. Pass externalId (your own id for the customer) to find theirs, then pass its id as profileId to list_accounts, connect_account and schedule_post. |
| Does it change anything? | Reads only. |
| Which endpoint does it call? | GET /v1/profiles |
| Which server? | https://mcp.flung.dev/mcp-oauth (sign in) or https://mcp.flung.dev/mcp (API key). |
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
externalId | string | no | Your own id for the customer. at least 1 character; at most 255 characters. |
limit | integer | no | Profiles per page. minimum 1; maximum 50; default 20. |
startingAfter | string | no | The last profile id of the previous page. at least 1 character; at most 64 characters. |
Example call
json
{ "name": "list_profiles", "arguments": { "externalId": "user_8412" }}Things a person might say
- "Which accounts does customer user_8412 have?"
Annotations
| Hint | Value |
|---|---|
readOnlyHint | true |
destructiveHint | false |
idempotentHint | true |
openWorldHint | false |
See also
| Doc | Why |
|---|---|
| MCP tools | Every tool |
| Connect an AI agent | Install the server in your client |
GET /v1/profiles | The same operation over HTTP |