What admins can ask.
Jobs the platform owner can hand to an AI client, with example requests, the tools behind them and the access each needs.
On this page
This page is for the platform owner. Each job below lists example requests, the tools the client uses, and the access it needs. Say it your own way.
You choose the access when you connect. Read everything covers every read on this page except stored-money amounts, which need Include money records. A job that changes something needs Read and make changes you approve, or a Custom connection that allows changes in that area. Risky changes wait for your approval. See Approvals.
The full tool list is in Admin tools. Every call shows in the connection's trail and in the activity log. See The activity trail.
Start a job in one click
Clients that support MCP prompts list these jobs for your connection, for example as slash commands. Choose one and the client starts the job with the steps already written. A prompt only gives the client its instructions. It adds no access, and risky changes still wait for your approval. A prompt appears only when your connection has every tool the job needs, so a connection with less access sees fewer.
| Prompt | What it does | Needs |
|---|---|---|
weekly_platform_report |
A short report on how the platform did this week: growth, revenue, what needs attention and system health. It only reads. | admin_get_platform_overview |
investigate_health |
Finds what is wrong with the installation, why, and what to do about it. It only reads. If you ask, it can run one scheduled task once, and that run needs no approval. | admin_get_health_report |
review_partner |
Reviews one business: its plan and billing, how it uses its programs, its activity and what needs attention. You give the business in the partner argument, as a name, an email or an id. For a connection that may read businesses, a client that supports completion suggests business names as you type. Moving the business to another plan or deactivating it waits for your approval. |
admin_get_partner and a business list or search tool |
past_due_follow_up |
Finds businesses whose payment is past due or whose trial ends soon, and drafts a follow-up for each. The client can't send email, so you send the drafts yourself. | admin_get_saas_overview |
member_lookup |
Finds a member by email, member number or identifier (the identifier argument) and summarizes their programs, balances and recent activity. It only reads. |
admin_get_member and a search or member list tool |
Check how the platform is doing
- "How did the platform do this week?"
- "Who is past due, and whose trial ends in the next 7 days?"
- "What did the activity log show over the last 30 days?"
The client uses admin_get_platform_overview, admin_get_saas_overview and admin_get_activity_analytics. They return what the admin dashboard, the Plans & billing page and the activity analytics show. Each figure comes with a note on how Reward Loyalty calculated it. Monthly recurring revenue is an estimate from plan list prices.
Access: reads only.
Check the health of the installation
- "Why is the Health center yellow?"
- "Which scheduled tasks are late?"
- "When did each scheduled task last run?"
- "Are webhook deliveries backed up?"
The client uses admin_get_health_report. It lists every Health center check with its status, and each scheduled task with its last run. It also gives the webhook backlog, the achievement reward backlog and the number of pending migrations. Reading it starts nothing.
A scheduled task runs without approval. Some tasks send member emails, issue rewards or expire points. Ask the client to name the task before it runs one.
To act on what it finds, the client can run one scheduled task now with admin_run_scheduled_task, or deliver waiting webhooks with admin_run_webhook_drain. This is the same as Run now in the Health center.
Access: reads for the report. Maintenance changes for the runs.
Find a business, a member or a ticket
- "Find the business with the email [email protected]."
- "Show me everything about [email protected]."
- "Which businesses signed up in the last 30 days?"
The client starts with admin_search, which looks across businesses, members, programs and support tickets by name, email, identifier or code. It then opens the match with admin_get_partner or admin_get_member. A member record shows cards, balances, stamps, vouchers, passes, tiers, achievements and email consent across every business. admin_get_member_ledger shows each transaction. For long lists the client uses the console's own lists, with the same filters and sorting, through admin_describe_records and admin_list_records.
Stored-money amounts appear only when the connection includes Include money records. Otherwise the answer says the amounts are hidden.
Access: reads only.
Read a business as that business sees it
- "What are the best stamp cards at Bakery Bob?"
- "How many members did Bakery Bob gain this month?"
The client uses admin_describe_partner_reads and admin_partner_read. They return what the business's own connection would get, limited by that business's plan. They only read. A change to a business goes through the admin tools instead.
Access: the Business data area, read only.
Manage businesses and plans
- "Create a business called Bakery Bob on the plan I name."
- "Give this business webhooks and raise its staff limit to 10."
- "Move this business to another plan."
- "Deactivate this business."
- "What would deleting this business remove?"
The client can create a business, update its profile and change its 25 permissions and limits. Moving a business to another plan, deactivating it and deleting it each wait for your approval. The review page lists the plan before and after, or what a delete would remove. admin_get_partner_delete_impact shows the same counts without deleting anything.
Access: Businesses area. Reads need read access. Changes need change access.
Correct a member's history
- "Undo the last points transaction on this member's card."
- "Delete this member."
The client can undo the last transaction, stamps, voucher redemption or pass visit, or delete a member. Each waits for your approval. For an undo, the client names the entry it read, and the change stops with a conflict if a newer entry arrived.
Access: Members area, with change access.
Answer support tickets
- "Which support tickets are still open?"
- "Add an internal note to this ticket."
- "Reply to this ticket and tell her the fix is live."
The client reads tickets through the console list. It can set a status or assignee and add an internal note without asking you. A reply to the person who raised the ticket sends an email, so it waits for your approval. The review page shows the exact email.
Access: Support area.
Change settings, plans and languages
- "Show me the current plans and their limits."
- "Add Dutch as a language."
- "Check the nl_NL translations that still need a text."
The client reads settings, plans and languages. It can change most settings, add or update a language and edit translations. Some settings wait for your approval: the app URL, who can sign up, the mail sender, the homepage layout and a few feature switches. Editing or resetting a plan, and changing or resetting the language policy, always wait for your approval.
A few settings can't be changed through an AI connection at all: credentials, uploads, the billing provider and the AI and Agent API switches. The client gets a refusal that names the setting.
Access: Platform area.
Check the license and updates
- "Is my license active, and which version am I on?"
- "Is there a newer release?"
The client reads the license status from what the last check stored. It can ask the license server for an update check or refresh the license status. It can't install an update, restore a backup or activate a license. Those stay on the license page.
Access: reads for the status. Maintenance changes for the checks.
Print member cards
- "List the printed card batches."
- "Generate 100 blank member cards for one business."
The client can list batches and codes, and generate cards for you or on behalf of a business. Disabling a card and deleting blank cards wait for your approval. This only works when member cards are on.
Access: Members area.
What an AI client can't do for you
Some tasks stay in Reward Loyalty on purpose, such as provider secrets, installing updates, passwords, creating keys and uploads. What stays out of reach has the full list. The What your AI can do section on the AI connections page lists each area and what stays with you.
Related topics
- Admin tools: every tool with its safety and access.
- Approvals
- Access and security