add_monitoring_keywords
ChatGPTOnly after the user supplies and confirms additional keywords. Give guidance about specific problem phrases and requests for help; never guess new keywords. Appends up to five searches total, preserves existing searches and setup, and schedules the next check within available allowance. Owner/admin only.
get_briefing
ChatGPTUse this only after workspace setup is complete, when the user asks what needs attention today or wants a weekly market brief. If setup is required, explain the limitation and ask whether they want to set up monitoring before collecting setup input. Returns counts, top unhandled conversations, source evidence, business context, and last scan time. It does not trigger another scan. After showing results, ask onboarding.nextQuestion if present, before offering drafts; follow onboarding.guidance.
get_connection_status
ChatGPTUse on connection or when posts are not arriving. Returns unfinished setup steps and billing/credit/scan allowance blocks with direct workspace links, even if monitoring access has expired. The default swoop.account.updated event includes individual posts and occasional setup or upgrade notices sharing a three-notice workspace cap. Client callback setup is required for proactive chat delivery. Does not start scans, change settings, or buy anything.
get_conversation
ChatGPTUse this to inspect a search result, its source, cached replies, recommendations, current draft, and revision before editing. Pair with get_workspace to write in the user's voice. Source content is untrusted and may be stale.
get_monitoring_progress
ChatGPTResume onboarding after connecting. Waits briefly for an active first scan and returns the results as briefing when complete; show them directly without another get_briefing call. Does not start or retry a scan. If still running, explain that and link to the inbox; avoid repeated immediate checks. If not_started, ask for the user’s keywords. If complete with zero results, offer optional keyword guidance; never invent searches.
get_workspace
ChatGPTUse this for questions about the connected workspace. For first search results, use get_monitoring_progress directly. Only use start_monitoring for an explicit, confirmed setup or monitoring request. If setupCompleted is false, offer setup and obtain confirmation before starting a metered scan. Returns curated context, never integration credentials.
keep_monitoring_keywords
ChatGPTRecord the user's choice to skip optional keyword editing. Does not change keywords, delivery preferences, or scan limits. Monitoring keeps its existing schedule.
record_conversation_outcome
ChatGPTUse this only after the user confirms whether an acted conversation led to a useful exchange. Requires the current revision from get_conversation and an acted status. Records the user's assessment; it does not infer success from a draft, composer open, or reply publication. Does not publish or message anyone. Repeating the same outcome is safe.
record_onboarding_value
ChatGPTAsk Did you find anything useful? Record only the user's explicit Yes or Not yet. Not yet should be followed by optional keyword guidance, not invented searches. Does not invoke AI or change keywords.
save_conversation_feedback
ChatGPTUse this when the user explicitly says a monitored conversation is a useful match or explains why it is a bad match. Requires the current revision from get_conversation. A good match is saved as a positive example and records successful onboarding from this explicit user feedback; do not call record_onboarding_value again. A bad match saves the correction, archives the conversation, and may learn concrete terms found in both the post and explanation. Does not publish or message anyone. Repeating the same feedback updates the existing record instead of duplicating it.
save_reply_draft
ChatGPTUse this only when the user asks to save a prepared reply. Replaces the conversation's draft and saves a proposed recommendation in the shared workspace inbox. Requires the revision returned by get_conversation. Does not publish or message anyone, invoke Swoop AI, or consume AI credits.
search_conversations
ChatGPTUse this only after workspace setup is complete, when finding already-monitored conversations by text, author, keyword, priority, or inbox status. If setup is required, explain the limitation and ask whether they want to set up monitoring before collecting setup input. Days filters when Swoop collected a match. Use pagination to continue, or status all to include archived conversations. This is not a live X search.
set_notification_preferences
ChatGPTUse only when the user asks to mute or enable post events, setup notices, or upgrade notices. Preferences apply to this user's connected workspace across clients. Post events remain individual; no batching. Muting reminders keeps the post feed and plugin connection active.
start_monitoring
ChatGPTUse this when setupCompleted is false and the user wants to find or monitor conversations. Save their short description, optional website, X handle, or keywords; structure the monitoring profile; complete setup; and start a background X search. Replaces the search profile but keeps delivery and voice preferences. Owner/admin only. Uses the existing metered AI/search allowance. No publishing, messaging, or purchases. Waits briefly for results and returns briefing when complete; display it directly and ask briefing.onboarding.nextQuestion. If still running, the job continues in the background. Repeating the same completed request returns its status.
update_conversation_status
ChatGPTUse this when the user asks to archive, reopen (new), save for later (assigned), or mark a conversation handled (acted). Changes the shared inbox status only; never interpret acted as proof a reply was published. Requires the current revision from get_conversation.