Limits & Processing Time
How long async jobs take, how pagination works, and how to keep token usage down.
Limits and processing times
Asynchronous tools
Some tools return immediately with a job ID rather than a finished result. Poll get_demo_status until processing completes.
convert_url_to_demo
10 to 20 minutes
convert_video_to_demo
Under 10 minutes
convert_images_to_demo
Under 5 minutes
personalise_demo
Under 5 minutes
create_hub
Under 5 minutes
Pagination
List tools are paginated. Defaults differ by tool, so ask for a page size or a limit when you want a specific number.
list_demos
100
repx_list_topics
40
repx_get_analytics
25
Keeping token usage down
Token usage comes from two places: the tool definitions your client loads, and the data each tool returns.
Enable only the tools you need. Every enabled tool adds to every request.
Be specific. "Analytics for [demo name], last 30 days" costs far less than "how are my demos doing", which makes the agent list and check everything.
Use the lightest tool.
get_demo_statusinstead ofget_demowhen you only need to know whether processing finished.Narrow large queries. Add date ranges, filters, or limits to
list_demos,list_leads,list_accounts,get_demo_analytics, andrepx_get_analytics.Start a new chat per task. Long conversations resend earlier tool results with every message.
Use a smaller model for routine work. Pulling leads or creating links does not need your most capable model.
Feature and plan requirements
Starter plan or above
All MCP tools
Connected CRM, Deals enabled
list_crm_pipelines, list_crm_stages, list_crm_deals
Alerts enabled, paid plan
list_alerts, create_alert, update_alert
Hubs enabled
create_hub
Creator role or above
list_themes
OAuth client, not M2M
list_workspaces, switch_workspace
Last updated
Was this helpful?