FoundRole Jobs - AI Job Search & Application Tracker

Official

by foundrole

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Create a job alert

job_alert_subscribe

Idempotent

Subscribe to job alerts for a saved search, choosing daily, weekly, or monthly frequency, so new matching jobs arrive automatically by email digest.

Instructions

Subscribes the authenticated user to job alerts for a specific saved job search.

Input:

job_search_id: The job search identifier to subscribe to (required). Accepts either the job search UUID or the composite job ID returned by jobs_search / jobs_details (format: "seo_id--job_search_id").
frequency: Alert frequency — one of daily, weekly, monthly (optional, defaults to "weekly")

Output: Returns the created or updated job alert with id, status, and frequency. Idempotent: calling this tool for an already-subscribed search updates the existing alert without creating a duplicate. An existing active alert with the same query text, location, company and filters, and at least the same radius, is returned instead of a new one, with the requested frequency applied to it.

Delivery: All of a user's alerts arrive together in one email digest, one section per alert. Each section applies every filter and the sort of its saved search, the same way jobs_search does; Pro-only filters apply while the user has Pro. A job appears in the digest once, even when it matches several alerts, and no email is sent when there are no new matches. The digest follows the most frequent alert, and arrives less often when the user has not used FoundRole for a while.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`frequency`	No	Alert frequency: daily, weekly, monthly (defaults to "weekly")
`job_search_id`	Yes	Job search UUID or composite job id ("seo_id--job_search_id") from jobs_search results

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobAlert`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.9Aug 6, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare idempotentHint=true and destructiveHint=false, but the description goes well beyond them: it spells out the exact idempotency rule (existing alert matched on query text, location, company, filters, and at least the same radius), that the requested frequency is applied to the returned alert, and the delivery semantics (one digest, deduplicated jobs, Pro-only filters, cadence).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Bold section headers (Input/Output/Delivery) front-load the purpose and required parameter, and the Input/Output blocks earn their place. The Delivery paragraph is informative but longer than needed to select and invoke this tool, describing email behavior that doesn't change the call itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, yet the description still covers idempotency, default frequency, accepted ID formats, and downstream delivery effects. Nothing an agent needs to invoke this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, and the description largely restates them (UUID vs composite ID format, default 'weekly'). It adds no syntax or validation detail the schema lacks, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Subscribes the authenticated user to job alerts for a specific saved job search' — which cleanly separates it from job_alert_unsubscribe, job_alert_unsubscribe_all, and job_alert_list. An agent can identify the action without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use (subscribe to a saved job search) and points to jobs_search / jobs_details as the source of the accepted composite ID format. It does not explicitly state when to prefer this over the unsubscribe siblings or what prerequisites apply, so it stops short of a full when/when-not statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.