monity.ai

Cancel the current editor-owned preview.

cancel_editor_preview

Watch a web page and alert the user when it changes: price drops, restocks, new posts or listings, status changes, competitor updates, any 'tell me when this page changes'. Creates a website monitor that keeps watching after this conversation ends: monity.ai checks the page on a schedule in its own cloud browser, keeps a full-page screenshot and a full HTML copy of the page for every check, and alerts only when the change matters (an AI summary says what changed). Subject to the account plan's monitor limit. compareType AUTO (default) covers most pages; VISUAL for pixel comparison, TEXT for keyword monitoring, HTML for markup diffs. To watch one element pass selector (a CSS selector). Express the full intent in one call: use notifyWhen for a natural-language alert condition ('price drops below $500'), or notifyConditions + outputExtractor/jsonPath for deterministic threshold alerts without AI.

create_monitor

Open the existing Monity task editor. Omit uuid to create a task in workspaceId. Does not save or load a website until the user acts.

open_task_editor

Permanently delete a monitor with all its checks, screenshots and HTML copies. This cannot be undone: confirm with the user first, and use pause_monitor instead when they only want it to stop checking.

delete_monitor

Who is connected and what their monity.ai plan allows: plan name, credit refresh date, active monitors used and slots left per workspace, check credits left (a check normally costs one), and the check frequencies the plan allows. Use it before creating a monitor or changing a frequency, and to explain a refused create.

get_account

Get the full detail of one specific check by id, shown as evidence the user can inspect: before/after screenshots with a comparison slider, the highlighted difference, the AI summary of what changed, extracted values (current + previous), and the full HTML copy Monity kept of the page. pageAccess says what the browser reached; when reachedContent is false the check saw a challenge, login or error page, so report that, not a change in content. Each call shows the check to the user as a card: call it once per check, and not for a check another result already shows (get_latest_result does). When you link to a check, use its checkUrl (its comparison in monity.ai), never the raw screenshot, diff or HTML file URLs.

get_check

List a monitor's past checks (newest first): timestamps, status, alerted flag, percent difference, errors. Use get_check for the full detail of one check. pageAccess says what the browser reached; when reachedContent is false the check saw a challenge, login or error page, so report that, not a change in content. To show one change to the user, open it once with get_check. When you link to a check, use its checkUrl (its comparison in monity.ai), never the raw screenshot, diff or HTML file URLs.

get_check_history

Get a monitor's most recent completed check: status, whether it alerted, the extracted output (current and previous value), AI summary, and artifact URLs (screenshots, diff image, HTML snapshot). This answers questions like 'what is the price now?' or 'did anything change?'. pageAccess says what the browser reached; when reachedContent is false the check saw a challenge, login or error page, so report that, not a change in content. Its result is already shown to the user as that check's card (summary, screenshot and a Compare before and after button): do not also call get_check for the same check. When you link to a check, use its checkUrl (its comparison in monity.ai), never the raw screenshot, diff or HTML file URLs.

get_latest_result

Get one monitor's configuration summary by uuid (type, frequency, threshold, extractor, labels, skills and their alert rules, timestamps).

get_monitor

Account-wide feed of completed checks, newest first, each already carrying its monitor (name + URL), the AI summary of what changed, and the extracted output. This is the tool to use for reporting questions — 'what changed this week?', 'summarise my monitors', 'which pages moved?' — because it answers them in ONE call. Do not loop get_check_history over every monitor for that. Call it once per question: each call shows its own card to the user. Defaults to alerts only, which is what 'what changed' means; set alertedOnly false only when the user asks about every check (e.g. 'did my monitors run?'), never to look for more changes. pageAccess says what the browser reached; when reachedContent is false the check saw a challenge, login or error page, so report that, not a change in content. To show one change to the user, open it once with get_check. When you link to a check, use its checkUrl (its comparison in monity.ai), never the raw screenshot, diff or HTML file URLs.

get_recent_changes