Tools and prompts
Every BetterFans Link MCP tool for OnlyFans, Fansly and Fanvue: what it reads or asks to write, when an agent should call it, and the prompts.
Product page: OnlyFans MCP server
The MCP server has 28 tools. Read tools call the same routes as the REST API, so they return the same data and the same errors. Write tools create an action. For a client that signs in with OAuth, the action always waits for a person to approve it. For a client that signs in with an API key, it waits unless the key has auto-approve on. See approvals.
One tool set serves OnlyFans, Fansly and Fanvue accounts. The account decides which platform a call reaches. Each tool lists the platforms it works for, here and in its _meta as link.betterfans/platforms. A call for an account on any other platform returns not_supported_on_platform.
| Tool | Kind | Platforms |
|---|---|---|
list_accounts | Read | OnlyFans, Fansly and Fanvue |
account_health | Read | OnlyFans, Fansly and Fanvue |
link_account | Creates a hosted link | OnlyFans, Fansly and Fanvue |
get_link | Read | OnlyFans, Fansly and Fanvue |
find_fans | Read | OnlyFans, Fansly and Fanvue |
get_fan | Read | OnlyFans, Fansly and Fanvue |
list_fan_lists | Read | OnlyFans, Fansly and Fanvue |
online_fans | Read | OnlyFans, Fansly and Fanvue |
list_chats | Read | OnlyFans, Fansly and Fanvue |
get_chat | Read | OnlyFans, Fansly and Fanvue |
search_messages | Read | OnlyFans and Fansly |
draft_message | Read | OnlyFans, Fansly and Fanvue |
revenue_summary | Read | OnlyFans, Fansly and Fanvue |
list_transactions | Read | OnlyFans, Fansly and Fanvue |
mass_message_performance | Read | OnlyFans and Fanvue |
top_content | Read | OnlyFans, Fansly and Fanvue |
link_performance | Read | OnlyFans, Fansly and Fanvue |
list_vault | Read | OnlyFans, Fansly and Fanvue |
search_api | Read | OnlyFans, Fansly and Fanvue |
describe_endpoint | Read | OnlyFans, Fansly and Fanvue |
call_api | Read | OnlyFans, Fansly and Fanvue |
search_docs | Read | OnlyFans, Fansly and Fanvue |
get_doc | Read | OnlyFans, Fansly and Fanvue |
send_message | Write, creates an action | OnlyFans, Fansly and Fanvue |
send_mass_message | Write, creates an action | OnlyFans and Fanvue |
unsend_message | Write, creates an action | OnlyFans, Fansly and Fanvue |
label_fan | Write, creates an action | OnlyFans and Fanvue |
get_action | Read | OnlyFans, Fansly and Fanvue |
Accounts
list_accounts
List accounts. List the creator accounts this workspace can use, on OnlyFans, Fansly and Fanvue, with each one's platform and plain status (healthy, needs_relink, ...). Start here: every other tool needs an accountId from this list.
Call it first, to get account ids and see which accounts are healthy.
Read. Calls List accounts, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
platform | enum | Optional. Only accounts on this platform. Default all. One of all, onlyfans, fansly or fanvue. |
Returns a list of Account objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"platform": "fansly"
}account_health
Account health. One account's status, counts, 30 day revenue and when it last synced. Use when a call fails with account_unavailable or before a long task.
On OnlyFans and Fansly it reads synced data, so it answers even while live calls for the account are stopped. On a Fanvue account it reads Fanvue live while the account is healthy, and otherwise answers with its status. Read status and follow what to do for each status.
Read. Calls Get account, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
Returns an AccountDetail object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "412345678"
}link_account
Link an account. Get a hosted link a creator opens to connect their OnlyFans, Fansly or Fanvue account. Pass platform to choose for them, or leave it out to let them pick. Returns a URL to send the creator and a linkId. Nothing is linked until they finish; check progress with get_link.
Use it when the user wants to connect a creator, or reconnect one that needs a relink. Pass platform when you know where the creator is; leave it out to let them pick.
Creates a hosted link. Calls Create link, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
note | string | Optional. Shown in the dashboard next to the link, for example the creator's name. Up to 200 characters. |
platform | enum | Optional. onlyfans, fansly or fanvue. Leave out to let the creator pick on the link page. |
Returns a HostedLink object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"note": "Rae Vale",
"platform": "fansly"
}get_link
Check a link. Progress of a hosted link from link_account: waiting, signing in, needs a code, connected (with the new accountId and its platform) or failed.
Use it after link_account, to see whether the creator finished.
Read. Calls Get link, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
linkId | string | Link id from link_account. |
Returns a HostedLink object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"linkId": "link_9QwE4rTy6UiO2pAs8DfG1hJk"
}Fans
find_fans
Find fans. Search or rank an account's fans by username or name, subscription status, spend or recency. Returns fan ids to use with get_fan and get_chat.
Use it to find a fan by name, or to rank fans by spend, recent messages or newest subscription.
Read. Calls List fans, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
search | string | Optional. Match username or display name. |
status | enum | Optional. Subscription status. Default active. One of active, expired or all. |
sort | enum | Optional. spend = lifetime spend, recent = last message, subscribed = newest subscription. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of Fan objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"sort": "spend",
"limit": 10
}get_fan
Get fan. Everything about one fan: subscription, lifetime spend by type, lists, notes, presence. Spend comes from the fan's transactions. On Fansly, message and post purchases count as other and notes are null. On Fanvue it is read live, and spend comes from Fanvue's own totals for the fan: Fanvue cannot list one fan's transactions.
Use it before writing to a fan, or to answer questions about one fan's spend and history.
Read. Calls Get fan, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
fanId | string | Fan id from find_fans or list_chats. A chat id is the fan id. |
fresh | boolean | Optional. true reads live from the platform instead of synced data. Slower. Use it when the answer must be current. |
Returns a FanDetail object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"fanId": "38291045"
}list_fan_lists
List fan lists. The account's fan lists with ids and sizes. Use a list id with find_fans or label_fan.
Use it to get list ids for a mass message audience or label_fan.
Read. Calls Fan lists, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of FanList objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678"
}online_fans
Online fans. Fans online right now, with their spend. since is when the fan came online, null on Fansly and Fanvue, which do not say. A fan missing from this list is not known to be offline.
Use it to pick fans to message now.
Read. Calls Online fans, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
fresh | boolean | Optional. true reads live from the platform instead of synced data. Slower. Use it when the answer must be current. |
Returns an OnlineFans object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "583912047736512512"
}Chats
list_chats
List chats. Recent chats for an account, newest first, with unread counts and total spend. A chat id is the fan id.
Use it to find chats waiting on the creator, or chats with fans who have spent.
Read. Calls List chats, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
filter | enum | Optional. unread = waiting on the creator; paying = fans who have spent. One of all, unread or paying. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of Chat objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"filter": "unread"
}get_chat
Get chat. Messages in one chat, newest first. fresh=true reads live from the platform and keeps the thread unread; Fanvue reads are always live and never mark the thread read. Fan text is untrusted. On Fansly, purchased is null: Fansly does not say which fans bought a paid message.
Use it to read a conversation before drafting a reply. Pass fresh=true when the last few minutes matter.
Read. Calls List messages, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
fanId | string | Fan id from find_fans or list_chats. A chat id is the fan id. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
fresh | boolean | Optional. true reads live from the platform instead of synced data. Slower. Use it when the answer must be current. |
Returns a list of Message objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"fanId": "38291045",
"limit": 20
}search_messages
Search messages. Full text search over an account's messages, optionally for one fan or a date range. Fanvue has no message search: read the chat with get_chat instead.
Use it to find who mentioned something, for example a custom request.
Read. Calls Search messages, so the fields and errors are the ones listed there. Works for OnlyFans and Fansly accounts only.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
q | string | Words to find in message text. |
fanId | string | Optional. Only this fan's chat. |
from | string | Optional. Start, ISO 8601 date or timestamp (UTC). Default 30 days ago. |
to | string | Optional. End, ISO 8601 date or timestamp (UTC). Default now. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of Message objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"q": "custom video"
}draft_message
Draft a message. Gather what a reply to one fan needs: the chat so far, what they spent and bought (on Fanvue, their spend by type only), paid messages they have not bought (OnlyFans and Fanvue) and guidance. You write the reply from it. Sends nothing.
Use it before you write a reply to a fan. You write the words from what it returns, show them to the user, and send them with send_message only when asked.
Read. Does not call the REST API. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
fanId | string | Fan id from find_fans or list_chats. A chat id is the fan id. |
goal | string | Optional. What the reply should achieve, for example: thank them for the tip and tease tonight's set. Up to 500 characters. |
fresh | boolean | Optional. true reads the chat live from the platform instead of synced data. Slower. |
Returns, in structuredContent: the fan (a FanDetail object), recentMessages newest first, purchases from the last 365 days, openPaidMessages the fan has not bought (always empty on Fansly), the goal you passed, guidance for the reply, and meta.
Example arguments
{
"accountId": "412345678",
"fanId": "38291045",
"goal": "Thank them for the tip and tease tonight's set"
}Money
revenue_summary
Revenue summary. Gross and net revenue for a period, split by type, as a time series, with top fans and the previous period for comparison. Net is what the creator keeps after the platform fee. Never add gross and net together. On Fansly, message and post purchases count as other.
Use it for any question about earnings over a period, and for comparisons with the period before.
Read. Calls Revenue summary, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
from | string | Optional. Start, ISO 8601 date or timestamp (UTC). Default 30 days ago. |
to | string | Optional. End, ISO 8601 date or timestamp (UTC). Default now. |
interval | enum | Optional. Bucket size for the series. One of day, week or month. |
Returns a RevenueSummary object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "583912047736512512",
"from": "2026-09-01",
"to": "2026-09-30",
"interval": "week"
}list_transactions
List transactions. Individual transactions (subscriptions, tips, paid messages, posts) with fan, gross, net and fee. On Fansly, message and post purchases have type other, and type=message or type=post is invalid.
Use it when you need single payments, for example every tip from one fan.
Read. Calls List transactions, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
from | string | Optional. Start, ISO 8601 date or timestamp (UTC). Default 30 days ago. |
to | string | Optional. End, ISO 8601 date or timestamp (UTC). Default now. |
type | enum | Optional. Only this kind of earning. One of all, subscription, tip, message, post, stream, referral or other. |
fanId | string | Optional. Only this fan's transactions. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of Transaction objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"type": "tip",
"fanId": "51820377"
}Content
mass_message_performance
Mass message performance. Mass messages with how many fans got them, viewed and bought, and the revenue each made. A mass message's numbers are totals; never add them to per-fan message numbers. On Fanvue, sort=revenue ranks windows holding up to 200 mass messages; for more, use a shorter window.
Use it to compare mass messages by reach, opens and sales.
Read. Calls Mass messages, so the fields and errors are the ones listed there. Works for OnlyFans and Fanvue accounts only.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
from | string | Optional. Start, ISO 8601 date or timestamp (UTC). Default 30 days ago. |
to | string | Optional. End, ISO 8601 date or timestamp (UTC). Default now. |
sort | enum | Optional. recent = newest first. One of recent or revenue. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of MassMessage objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"sort": "revenue",
"limit": 10
}top_content
Top content. Posts ranked by likes or recency (recency only on Fanvue), with price, likes and comments. Revenue is null on every platform; tips are set on Fansly and Fanvue and null on OnlyFans.
Use it to see which posts do best.
Read. Calls Top content, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
from | string | Optional. Start, ISO 8601 date or timestamp (UTC). Default 30 days ago. |
to | string | Optional. End, ISO 8601 date or timestamp (UTC). Default now. |
sort | enum | Optional. recent = newest first, likes = most liked first. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of Post objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "583912047736512512",
"sort": "likes",
"limit": 10
}link_performance
Tracking link performance. Tracking and free trial links with clicks, subscribers and revenue.
Use it to compare tracking and trial links by subscribers and revenue.
Read. Calls Tracking links, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
sort | enum | Optional. revenue = most earned first. One of revenue, subscribers or recent. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of TrackingLink objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"sort": "subscribers"
}list_vault
List vault. Vault media with folders, how often each was sent and what it earned. Use media ids in send_message.
Use it to find media ids to attach to a message.
Read. Calls Vault, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
folder | string | Optional. Vault list id. Leave out for all media. |
type | enum | Optional. Media type. One of all, photo, video, audio or gif. |
cursor | string | Optional. nextCursor from the previous page. Leave out for the first page. |
limit | integer | Optional. Page size, 1 to 100. Default 25. |
Returns a list of VaultItem objects in structuredContent.data, with hasMore, nextCursor and meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"type": "video"
}Platform API
search_api
Search the platform API. Search our catalog of read-only OnlyFans, Fansly or Fanvue API endpoints by what you want to do. Pass platform, or an accountId to use its platform. Use before call_api. Needs a live key and a linked account on that platform.
Use it when no dedicated tool covers the data you need. Find the endpoint first. The catalog lists read (GET) endpoints only. An endpoint the platform has stopped using comes last and is marked removed. It needs a live key and a workspace with at least one linked account; otherwise it returns a missing_permission tool error.
Read. Does not call the REST API. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
query | string | What you want to find out, in plain words, for example: who bought a paid post. 1 to 200 characters. |
platform | enum | Optional. Which platform's API: onlyfans, fansly or fanvue. Leave out to use accountId's platform, or the only platform your workspace has linked. |
accountId | string | Optional. Account id from list_accounts; picks that account's platform. |
limit | integer | Optional. How many endpoints to return. Default 8. 1 to 25. |
Returns query, the platform it searched and results in structuredContent. Each result has the endpoint id to pass on (endpoint), its path, purpose, what it returns, how it pages (pagination) and a match score, plus removed when the platform has stopped using it.
Example arguments
{
"query": "who bought a paid post",
"accountId": "412345678"
}describe_endpoint
Describe a platform endpoint. Parameters, response fields and gotchas for one endpoint from search_api, on the same platform. Needs a live key and a linked account on that platform.
Use it after search_api, to learn an endpoint's parameters before call_api. When the platform started using an endpoint recently, since is the date. When it has stopped, removed is true and removedOn is the date when known, and the platform may change or drop the endpoint, so prefer another one for the same data. Like search_api, it needs a live key and at least one linked account, and returns missing_permission otherwise.
Read. Does not call the REST API. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
endpoint | string | Endpoint id from search_api, for example GET /chats/{chatId}/messages. A bare path works too. 1 to 300 characters. |
platform | enum | Optional. Which platform's API: onlyfans, fansly or fanvue. Leave out to use accountId's platform, or the only platform your workspace has linked. |
accountId | string | Optional. Account id from list_accounts; picks that account's platform. |
Returns the platform and the endpoint in structuredContent: its path, purpose, path and query parameters (pathParams, params), key response fields, what it returns, how it pages, its gotchas, and since, removed and removedOn when they apply. related lists endpoints for nearby data, relationships says how its ids connect to other endpoints and general holds the rules for every call on that platform.
Example arguments
{
"endpoint": "GET /chats/{chatId}/messages",
"accountId": "412345678"
}call_api
Call the platform API. Run a read-only API GET on the account's own platform, for an endpoint search_api finds. Prefer the dedicated tools; use this for data they do not cover.
Use it after describe_endpoint, with the path and the parameters it lists: a query parameter the endpoint does not take returns invalid_parameter. The answer warns when the platform has stopped using the endpoint.
Read. Calls Call OnlyFans, Call Fansly or Call Fanvue, by the account's platform, so the errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
path | string | API path relative to the platform's API root with the ids filled in, for example chats/123/messages on OnlyFans, messaging/groups on Fansly or chats on Fanvue. No query string. 1 to 500 characters. |
query | object | Optional. Query parameters, for example {"limit": 10, "order": "desc"}. A JSON object. |
Returns text only, with no structuredContent: the platform's JSON response inside a fan-written text tag, since anything in it can come from a fan, then where it came from and the request id. A long response is cut short and says so; ask for fewer items with limit.
Example arguments
{
"accountId": "412345678",
"path": "chats/38291045/messages",
"query": {
"limit": 10,
"order": "desc"
}
}Docs
search_docs
Search docs. Search BetterFans Link documentation and guides.
Use it when unsure how BetterFans Link behaves, for example what an error means.
Read. Does not call the REST API. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
query | string | What you want to know, for example: verify webhook signatures. 1 to 200 characters. |
limit | integer | Optional. How many pages to return. Default 5. 1 to 10. |
Returns query and results in structuredContent, each with the page slug, title, description, url and uri. Each page also comes back as a resource link.
Example arguments
{
"query": "verify webhook signatures"
}get_doc
Get doc. Read one documentation page as markdown.
Use it to read a page search_docs found.
Read. Does not call the REST API. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
slug | string | Page slug from search_docs, for example webhooks/verify. A docs URL or bfl://docs/ URI works too. 1 to 300 characters. |
Returns the page as markdown in the text, and in structuredContent as markdown with the page slug, title and url.
Example arguments
{
"slug": "webhooks/verify"
}Writes and approvals
send_message
Send message. Ask to send a message with optional vault media to one fan. On OnlyFans and Fanvue it can be paid (priceCents; on Fanvue with media). Creates an action a person approves before anything is sent, and returns the approval link. A key with auto-approve on sends at once and returns the result.
Use it when the user wants a message sent to one fan, with the exact text they agreed to.
Write, creates an action. Calls Create action, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
fanId | string | Fan id from find_fans or list_chats. A chat id is the fan id. |
text | string | The message. 1 to 5000 characters. |
priceCents | integer | Optional. Set to make it a paid message (PPV). OnlyFans and Fanvue, minimum 300. On Fanvue a paid message needs media. 0 to 2000000. |
mediaIds | array of strings | Optional. Vault media ids from list_vault. Up to 50 items. |
Returns an Action object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"fanId": "38291045",
"text": "Here is the custom clip you asked about",
"priceCents": 1500,
"mediaIds": [
"3399120045"
]
}send_mass_message
Send mass message. Ask to send a mass message to lists (or, on OnlyFans, to fans). Needs approval unless the key auto-approves. Returns the approval link (or the result) and estimated recipients.
Use it when the user wants one message sent to lists or many fans, with the exact text they agreed to.
Write, creates an action. Calls Create action, so the fields and errors are the ones listed there. Works for OnlyFans and Fanvue accounts only.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
text | string | The message every recipient gets. 1 to 5000 characters. |
priceCents | integer | Optional. Set to make it a paid message (PPV). Minimum 300. On Fanvue a paid message needs media. 0 to 2000000. |
mediaIds | array of strings | Optional. Vault media ids from list_vault. Up to 50 items. |
audience | object | Who gets it. Pick at least one list or fan. |
audience.listIds | array of strings | Optional. Fan list ids from list_fan_lists. |
audience.excludeListIds | array of strings | Optional. Fan list ids from list_fan_lists whose fans are left out. |
audience.fanIds | array of strings | Optional. Fan ids from find_fans. Up to 1000 items. |
Returns an Action object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"text": "Weekend special: the full beach video is in your inbox",
"priceCents": 1200,
"mediaIds": [
"3399120045"
],
"audience": {
"listIds": [
"994512"
],
"excludeListIds": [
"994530"
]
}
}unsend_message
Unsend message. Ask to take back a message, or on OnlyFans and Fanvue a whole mass message. Needs approval unless the key auto-approves.
Use it when the user wants a sent message, or a whole OnlyFans mass message, taken back.
Write, creates an action. Calls Create action, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
messageId | string | For an OnlyFans or Fanvue mass message, pass its massMessageId to unsend every copy. |
fanId | string | Optional. The fan whose chat holds the message. On OnlyFans and Fanvue, leave it out only to unsend a mass message by its massMessageId. |
Returns an Action object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"messageId": "118823004"
}label_fan
Add or remove a fan from a list. OnlyFans and Fanvue accounts (on Fanvue, its custom lists). Ask to add a fan to a list or remove them. Needs approval unless the key auto-approves.
Use it to sort fans into lists, so a mass message can go to a list or leave it out.
Write, creates an action. Calls Create action, so the fields and errors are the ones listed there. Works for OnlyFans and Fanvue accounts only.
| Argument | Type | Description |
|---|---|---|
accountId | string | Account id from list_accounts: the creator's user id on its platform. Always a string; Fansly ids are too long for a number and Fanvue ids are UUIDs. |
fanId | string | Fan id from find_fans or list_chats. A chat id is the fan id. |
listId | string | List id from list_fan_lists. |
operation | enum | add = put the fan on the list, remove = take them off. |
Returns an Action object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"accountId": "412345678",
"fanId": "38291045",
"listId": "994512",
"operation": "add"
}get_action
Get action. Check whether a write was approved, rejected or executed, and its result.
Use it after a write tool, to see whether a person approved it and what happened.
Read. Calls Get action, so the fields and errors are the ones listed there. Works for OnlyFans, Fansly and Fanvue accounts.
| Argument | Type | Description |
|---|---|---|
actionId | string | Action id returned by a write tool. |
Returns an Action object in structuredContent.data, with meta, and the same data as text.
Example arguments
{
"actionId": "act_8KpQ2wLz5XnR7cVb3MhT9dYs"
}Prompts
Prompts are ready-made requests your MCP client can show as commands. Each one runs the read tools it needs and reports back.
| Prompt | What it does |
|---|---|
daily_briefing | Daily briefing. Yesterday's revenue, top fans, unread chats worth answering and account problems. |
whale_report | Whale report. The top spenders, what they buy and who has gone quiet. |
reply_suggestions | Reply suggestions. Draft replies for the unread chats with paying fans. |