Emploist

Most tools are cleanly scoped to a resource plus action (jobs, applications, stages, comments, notifications, settings), and descriptions draw useful lines such as change_job_status (lifecycle) versus update_job_details (field edits). The weak spots are the near-twin names set_stage_email vs set_stage_emails (per-stage toggle versus company-wide switch), rank_application vs rank_waiting_applications, and get_overview vs get_stats, which rely on careful reading rather than obvious naming.

Names follow a predictable snake_case verb_noun pattern (list_jobs, get_job, add_stage, move_application, set_ai_ranking). The only real deviation risk is singular/plural pairs like set_stage_email/set_stage_emails, where one letter carries the entire semantic difference, plus inconsistent verb choices across the same concept (edit_comment vs update_job_details).

Thirty tools is heavy for an ATS surface and lands above the comfortable range, even though nearly every one maps to a distinct operation. Some are niche (set_reply_to, undo_move, rank_application) and could be folded into broader settings or application tools, so the set feels somewhat sprawling rather than tightly scoped.

Lifecycle coverage is strong: jobs (create/get/list/update/status/duplicate/delete), stages (add/rename/reorder/delete), applications (list/get/move/undo/delete), comments CRUD, settings, stats, overview, and team. Minor gaps remain — no application rejection/withdrawal action distinct from stage moves, no way to mark or clear notifications, and no search across jobs or applicants.