Tools reference

Your AI assistant picks the right tool based on what you ask. You don’t need to name tools yourself. Only the committee owner can connect. Invited Members and Admins can’t use these tools.

Account and events

Tool	What it does	Try asking
`get_account`	Shows the signed-in organizer and their committee.	”Which Taack account am I connected as?”
`list_events`	Lists events you can manage, with dates, venue, and visibility. Returns up to 25 by default, 50 at most.	”List my upcoming events.”
`get_event`	Shows full details for one event, including its saved Next Steps.	”Show me the details and Next Steps for Carnival Friday Fete.”
`create_event`	Creates a new event as a private draft.	”Create a draft event called Boat Ride Saturday on 14 March at 2 PM.”
`update_event`	Edits event details and Next Steps, and can publish the event.	”Move Boat Ride Saturday to 3 PM and publish it.”
`search_venues`	Searches Taack’s saved venues by name, address, or city.	”Find venues in Port of Spain called Savannah.”

create_event always creates a private draft. The event stays hidden from patrons until you ask the assistant to publish it, or you publish it from the dashboard.

When you name a place, the assistant searches saved venues first. A saved venue gives your event a map pin and directions. If nothing matches, it saves the place as plain text, and you can set the exact location later in Events.

Next Steps

Ask the assistant to read Next Steps with get_event or change it with update_event. For example: “Set the Next Steps title to ‘What to bring’, add a kit list, and turn it on for Saturday’s walk.”

enabled turns the message on or off. Turning it off keeps the content.
title is required when enabled and allows up to 100 characters.
description accepts plain text or simple markdown: bold, italic, links, lists, and paragraphs. An empty string clears it.
buttons allows up to two buttons, each with a label of up to 40 characters and an HTTPS, email, or telephone link.
showWhilePendingApproval defaults to false. On approval-required events, true also shows Next Steps on checkout complete for pending RSVP requests without a payment plan. Plan requests still need approval and a paid deposit. It does not change email or ticket-page eligibility.

Fields you omit keep their saved values. Sending buttons replaces the entire button list, so include every button you want to keep. To preserve an existing button’s tap history, pass its id from get_event; the connector can also match its existing label or link. An empty list removes all buttons and their counts. The assistant receives the saved Next Steps after an update so you can check the result. create_event does not accept Next Steps; create the draft first, then update it. There is no separate Next Steps tool, and the connector does not return button tap counts. Open the event’s Checkout or Registration tab to see those counts. See Next Steps for visibility, editing, and transfer rules.

Tickets

Tool	What it does	Try asking
`list_ticket_types`	Lists an event’s ticket types with price, currency, quantity, sold, and remaining.	”How many VIP tickets are left?”
`create_ticket_type`	Adds a ticket type with a name, price, currency (TTD, JMD, or USD), and quantity.	”Add 150 Early Bird tickets at 200 TTD.”
`update_ticket_type`	Changes a ticket type’s name, price, currency, or quantity.	”Raise General to 300 TTD and add 50 more.”

A few rules apply to tickets created through the connector:

Quantity defaults to 100 if you don’t give one.
Fees default to Absorb fees, the same as the dashboard. To use Split 50/50 or Pass on fees, change it in the dashboard.
All ticket types on one event must use the same currency.
You can’t lower a quantity below the number already sold.
Set how many tickets you’ll sell with ticket types. The event itself doesn’t store a capacity.

Sales

Tool	What it does	Try asking
`get_sales_summary`	Shows tickets sold and revenue for an event, broken down by ticket type, plus tickets held on payment plans.	”How are sales going for Carnival Friday Fete?”

Custom checkout questions

Tool	What it does	Try asking
`list_custom_questions`	Lists the event’s questions, types, required and multi-select settings, and available options.	”What questions do patrons answer for Saturday’s walk?”
`get_custom_question_results`	Counts answers for all questions or one selected question. Can split option counts by ticket type.	”How many patrons selected the shuttle, split by ticket type?”
`list_custom_question_responses`	Lists answers to one question with buyer contact details, ticket type, and payment status.	”Show the answers from patrons who selected the shuttle.”

These tools read existing questions and responses. Use Checkout or Registration on the event to set up questions. Results separate paid tickets, which are fully paid, from onPlan tickets held by a payment plan still in progress. Report the two separately. Results include answered and unanswered counts, plus otherValues for answers that no longer match a current option. Multi-select questions can have more selections than attendees who answered. Text and website question results show counts; use the response tool to read their answers. The response tool can filter by an exact option, ignoring case, or by text contained in a text answer. It returns the first 25 matches by default, up to 50. matching gives the number of matches found; returned gives the number listed. There is no next-page cursor. Narrow the answer filter or use the results tool for totals. A truncated scan means even matching and totals are minimum figures. The buyer contact is the patron who bought the ticket and may differ from the attendee who answered. Use these details for your own follow-up; the assistant cannot message patrons.

Payment plans

Tool	What it does	Try asking
`list_payment_plans`	Lists payment plans with the patron, status, amounts, and next due date. You can filter by event, status, or patron name or email.	”Show active payment plans for Carnival Friday Fete.”
`get_payment_plan`	Shows one plan in full: every scheduled payment, the grace period, and the missed-payment policy.	”Show the full schedule for Jordan’s payment plan.”
`get_payment_plan_stats`	Totals money collected and still outstanding across active and past-due plans, and flags plans with problems.	”How much is still owed on payment plans?”
`list_overdue_payment_plans`	Lists plans with a late payment, most overdue first.	”Who’s behind on their payment plan?”
`get_upcoming_plan_payments`	Lists payments coming due in the next 30 days by default, up to 180 days.	”What payment-plan money is due this month?”

Payment-plan tools are read-only. They show patron names and email addresses so you can follow up yourself. The assistant won’t message patrons for you. To cancel a plan, open the event in Events, then choose More → Payment Plans.

How the connector reports money

The connector’s sales summary separates fully paid ticket revenue from money collected on payment plans still in progress. Taack tells your AI assistant to keep these figures separate when it answers you.

Revenue counts fully paid tickets only

get_sales_summary counts a ticket as sold, and adds it to revenue, only once it’s paid in full. Tickets reserved on a payment plan that’s still in progress show as held, not sold.

Payment-plan money gets its own line

get_sales_summary excludes deposits and payments collected on in-progress plans from its ticket revenue. The assistant reports this collected money on its own line, next to paid sales, and never adds the two together. Once the patron pays the full balance and Taack issues the tickets, the plan’s completed sale appears in ticket revenue. The dashboard’s Online Earnings and Payouts can include money already collected on active or past-due plans before tickets are issued. Those figures can therefore differ from the connector’s fully paid ticket revenue. Future payments that have not been collected are outstanding amounts, not collected earnings. See Payment plans.

The connector never adds amounts in different currencies together. 500 TTD plus 100 USD is not 600 of anything. The connector reports each amount in its own currency. When it gives one combined figure, that figure is a TTD equivalent and says so.

Truncated results

Lists return a limited number of rows, and the connector may stop counting very large totals early. When that happens, the connector marks the result as truncated, and the assistant should tell you. Treat a truncated figure as a minimum, not a complete total. To get a complete answer, ask about one event at a time or narrow the question. For example, ask for “past-due plans for Carnival Friday Fete” instead of “all payment plans”. See Troubleshooting.

Getting started

For organizers

AI assistants (MCP)

For patrons

Reference

Account and events

Next Steps

Tickets

Sales

Custom checkout questions

Payment plans

How the connector reports money

Revenue counts fully paid tickets only

Payment-plan money gets its own line

Truncated results

​Account and events

​Next Steps

​Tickets

​Sales

​Custom checkout questions

​Payment plans

​How the connector reports money

​Revenue counts fully paid tickets only

​Payment-plan money gets its own line

​Truncated results

Account and events

Next Steps

Tickets

Sales

Custom checkout questions

Payment plans

How the connector reports money

Revenue counts fully paid tickets only

Payment-plan money gets its own line

Truncated results