Skip to main content
Attach these descriptions to each Autoplay MCP tool so the agent calls it with the right intent and interprets its result correctly. The exact field name varies by agent provider.

get_live_user_activity

This tool answers what the user is doing now. It does not determine their overall onboarding priority or decide whether the agent may initiate contact.

get_onboarding_context

This tool answers what is genuinely next. It does not authorize agent-initiated contact.

get_proactivity_criteria

This tool answers whether the agent may interrupt now. It does not choose the recommendation by itself.

Keep identity out of the conversation

All three tools require:
  • product_id: the fixed Autoplay product identifier associated with the authenticated connection.
  • user_id: the exact stable application ID from verified session context, matching the ID sent by the activity source.
Do not configure either value as information the agent should collect from the user. Never substitute an email, display name, conversation ID, or guessed value. If the agent provider cannot bind verified identity to the tool argument, resolve that integration gap before enabling personalized recommendations.

Verify the behavior

Test three separate paths:
  1. Ask a question about the current screen and confirm the agent uses live activity without exposing raw events.
  2. Ask what to do next and confirm the agent does not recommend a completed or in-progress milestone.
  3. Attempt an agent-initiated message when can_be_proactive_now is false and confirm no message is sent.

Review the complete prompt

See how these tool instructions fit into the provider-neutral conversation behavior.