NotifyAI

Create a recurring job monitor that watches for new matching jobs and notifies the user by email as they appear. Use this whenever the user wants to be alerted, notified, tracked, or kept updated about future job postings - as opposed to search_jobs, which only looks at jobs that exist right now. A monitor uses one or more keywords and can also be narrowed by location, work type, specific companies, or a careers page URL. If the user hasn't given a notification frequency, default to 'daily' and tell them what default was used rather than silently picking one. Always summarize the monitor you are about to create in plain language and get explicit confirmation from the user before calling this tool, since it creates a standing subscription that will send them emails. Creates a new job monitor for the current user. A monitor must include at least one keyword. Additional matching criteria include: - Companies - Locations - Work/Job type default includes (remote-specific-country, On-Site, Hybrid), remote-specific-country, remote-worldwide, Hybrid, On-site. Choose one appropriately - URL (for monitoring a specific career page) - Notification Frequency (hourly, daily, weekly, fortnightly, monthly). Choose one If the user does not provide a keyword, ask for one before calling this tool. A URL alone is not sufficient. When creating a URL monitor, the user must also provide one or more keywords to match jobs on that page. A URL without keywords cannot identify relevant jobs and should not be submitted. Validate all required fields before invoking the tool. If any required information is missing, ask the user for the missing details instead of making the API call.

Permanently delete a monitor. This cannot be undone - the user would need to create a new monitor from scratch. Always confirm explicitly with the user before calling this, stating which monitor (by name/criteria) is about to be deleted. Permanently deletes a monitor. Use this tool only after the user has clearly identified the monitor they want to delete and has confirmed the deletion. If the user does not uniquely identify the monitor, first use the "List Monitors" tool to help them select the correct monitor. This operation is irreversible. Once deleted, the monitor and its associated configuration cannot be recovered. This tool assumes any required user confirmation has already been obtained during the conversation. It performs the deletion immediately and does not ask for confirmation itself.

Edit an existing monitor's criteria (keywords, locations, companies, url, worktype) or its notification frequency. The API replaces the complete configuration, so retrieve the existing monitor and merge the requested change before calling this tool. If the user's reference to the monitor is ambiguous (e.g. 'the Bangalore one' and there are two), call list_monitors first to resolve it, and confirm which one with the user if still unclear. Always confirm the specific change in plain language before calling this tool, since it alters a live subscription. Updates an existing monitor. This API performs a full overwrite of the monitor configuration, not a partial patch. Before calling this tool, retrieve the existing monitor configuration and merge the user's requested changes into it. Then send the complete updated monitor object. Examples: - If the user asks to add a location, include all existing locations plus the new one. - If the user asks to remove a location, include all remaining locations. - The same rule applies to keywords, companies, work types, frequency, and all other editable fields. Do not send only the fields that changed. Any omitted field may be overwritten or cleared. The monitor type cannot be changed. For example: - A Roles monitor cannot be converted into a Company monitor. - A Company monitor cannot be converted into a URL monitor. - A URL monitor cannot be converted into any other monitor type. If monitor type is "roles" - Keywords, locations, worktype and frequency params are required If monitor type is "companies" - Keywords, locations, companies, worktype and frequency params are required If monitor type is "url" - Keywords, url, frequency params are required Each monitor type requires a specific set of fields. Preserve all required fields for the existing monitor type when constructing the update request. The API will reject requests that omit required fields.

Fetch full details of a single monitor by its ID, including its match history / recent results if available. Use this when the user asks about a specific monitor's status, last-checked time, or what it has found so far. Fetches the complete details of a specific monitor. Use this tool when the user wants to: - View a monitor's configuration. - Inspect the monitor's recent job matches. - Review monitor settings before editing or renaming it. - Understand why a monitor is or isn't matching jobs. If the user does not uniquely identify the monitor, first use the "List Monitors" tool to help them select the correct one. This tool is read-only and does not modify the monitor.

List the user's existing job monitors, optionally filtered by status (active, paused). Use this whenever the user asks what they're monitoring, wants an overview of their alerts, or when you need to resolve a fuzzy reference like 'the Google one' or 'the Bangalore monitor' before calling edit_monitor, pause_monitor, resume_monitor or delete_monitor. This is read-only and safe to call without confirmation. Lists all monitors belonging to the current user. This tool returns both active and inactive monitors in a single list, sorted from newest to oldest. Use this tool whenever the user refers to a monitor without uniquely identifying it. For example: - "Delete my Google monitor." - "Pause my software engineer monitor." - "Resume my monitor." - "Edit my monitor." The returned list allows the user to identify the correct monitor before another action (edit, rename, pause, resume, or delete) is performed. This tool is also useful when the user wants to: - View all of their monitors. - See which monitors are active or inactive. - Decide which monitor to pause, resume, edit, rename, or delete.

Health check for NotifyAI MCP Server.

Renames an existing monitor. The monitor name is a human-readable label that helps users identify and manage their monitors. Choose a concise and descriptive name that clearly reflects what the monitor tracks. Requirements: - Must contain between 3 and 60 characters (inclusive). - Should be meaningful and easy for the user to recognize when they have multiple monitors. If the user provides a name that does not meet the length requirement, ask them for a valid name before calling this tool.

Search jobs available on NotifyAI. WHEN TO USE Use this tool whenever the user wants to find, browse, explore, or discover job opportunities. Users may search using any combination of job titles, skills, companies, locations, or work arrangements (remote, hybrid, on-site). If the user has not provided enough information to perform a useful search, ask follow-up questions instead of guessing. Only invoke this tool once sufficient search intent has been collected. INPUT EXPANSION — BROADEN BY DEFAULT Unless the user's request is already narrow (see "Narrowing signals" below), expand these fields with closely related terms before calling this tool, so results aren't limited to an exact string match: - keywords: include common synonyms, adjacent job titles, and standard abbreviations for the role named. Example: "software engineer" → also include terms like "SDE", "SDE1", "Backend Engineer", "Python Developer" as relevant to context. "Product Manager" → also include "PM", "APM", "Senior Product Manager". Add at most 3-5 closely related terms — stay on the same role family, don't drift into unrelated roles. - locations: if the user names a specific city, also include its natural wider metro area, state, or region so nearby postings aren't missed. Example: "San Jose" → also include "California", "Bay Area". Don't add unrelated regions (e.g. don't add "New York" for a "San Jose" search). - companies: if the user names a specific company, consider including 2-4 well-known direct competitors so adjacent opportunities aren't missed. Example: "Google" → also include "Meta", "Amazon", "Microsoft" as relevant to the role/industry context. NARROWING SIGNALS — DO NOT EXPAND Do not add related keywords, locations, or companies when: - the user uses exclusive language: "only", "just", "exactly", "specifically", "strictly"; - the user is refining or filtering a previous search or monitor (e.g. "now just show me the Google ones", "narrow that to San Jose only"); - the user provides an unusually precise or niche title/location/company that suggests they already know exactly what they want. When you do expand the search, briefly tell the user what related terms you included in one short sentence, and note they can ask you to narrow to the exact term if they'd prefer. Do not list every added term in detail — keep this mention brief. RESULT PRESENTATION (must render consistently across any AI client — Claude, ChatGPT, Cursor, or other MCP-compatible assistants) Present each returned job as a compact, scannable Markdown block — never as raw JSON or a dense paragraph. Use standard Markdown syntax only (bold, line breaks, links) so formatting degrades gracefully in any client, even ones without custom card rendering. Each job entry must contain, in this order: 1. **Job Title** — bold, first line 2. Company name 3. Location • Work Type • Posted Date — one line, separated by " • " 4. Optional short line of additional metadata only when it adds real value (e.g. salary range, if present) 5. A clickable action using standard Markdown link syntax, always pointing to the job's `job_link.url`: [View Job →](job_link.url) Template: **[Job Title]** Company Name Location • Work Type • Posted Date [View Job →](job_link.url) RULES - One entry per job, separated by a blank line for scannability. - Never expose internal fields (IDs, checksums, raw location arrays) — use `display_location` when available instead of raw location arrays. - Every job entry must include its own "View Job" link — never omit it, never share one link across multiple jobs. - When more than 10 jobs match, show the top 5-10 most relevant first. - State the total number of matches once, above or below the set of entries — not repeated per entry. - If more results exist beyond what's shown, tell the user additional jobs are available and offer to show more. - Avoid showing Ids provided in result set.

Pause or resume a monitor. A paused monitor keeps its saved criteria but stops checking for new jobs and sending notifications until resumed. Use this when the user asks to pause, stop, mute, resume, restart or reactivate a monitor. Confirm which monitor and the intended new status before calling. Changes the status of a monitor between active and inactive. Use this tool when the user wants to: - Pause a monitor. - Resume or reactivate a paused monitor. - Enable or disable job notifications for a monitor. This tool only changes the monitor's status. It does not modify any other monitor settings. If the user does not uniquely identify the monitor, first use the "List Monitors" tool to help them select the correct monitor. Do not use this tool to delete a monitor. Deletion is handled separately by the "Delete Monitor" tool.