Free resume tools: ATS score, job match, bullet and LinkedIn checks, tailoring, interview prep.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Use this when the user wants stronger verbs or synonyms for resume wording. Suggest resume action verbs. Pass a weak opener ("responsible for", "helped") for direct swaps and why they read weak, or the work in plain words ("trained new staff", "cut costs") for the matching verb groups with an example bullet. Leave query empty for every group.
Optional. A weak verb or phrase, or the kind of work in plain words.
Use this when the user wants stronger verbs or synonyms for resume wording. Suggest resume action verbs. Pass a weak opener ("responsible for", "helped") for direct swaps and why they read weak, or the work in plain words ("trained new staff", "cut costs") for the matching verb groups with an example bullet. Leave query empty for every group.
| Argument | Type | Description |
|---|---|---|
| query | string | Optional. A weak verb or phrase, or the kind of work in plain words. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"query": {
"type": "string",
"maxLength": 200,
"description": "Optional. A weak verb or phrase, or the kind of work in plain words."
}
}
}Use this when the user wants a few resume bullet points checked without sending the whole resume. Give each resume bullet a score, a verdict and specific fixes with stable codes: weak openers, missing scale or result, numbers that show neither, hard-to-believe claims, first person, vague claims. The same rules and severities as check_resume. Up to 30 bullets of up to 600 characters each; blank items are skipped and reported by index. Rules version 2026-10-23.5.
| Argument | Type | Description |
|---|---|---|
| bullets* | array | One resume bullet per item, at most 30. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"bullets"
],
"properties": {
"bullets": {
"type": "array",
"items": {
"type": "string",
"maxLength": 600
},
"maxItems": 30,
"minItems": 1,
"description": "One resume bullet per item, at most 30."
}
}
}Use this when the user wants their LinkedIn About or summary section reviewed. Check a LinkedIn About section: what shows before "see more" on a phone and on a computer, whether the opening says who they are, results with numbers, buzzwords, a clear next step, and the 2,600-character limit.
| Argument | Type | Description |
|---|---|---|
| role | string | Optional. The job title the user wants to be found for. |
| about* | string | The whole About section. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"about"
],
"properties": {
"role": {
"type": "string",
"maxLength": 200,
"description": "Optional. The job title the user wants to be found for."
},
"about": {
"type": "string",
"maxLength": 6000,
"minLength": 1,
"description": "The whole About section."
}
}
}Use this when the user wants their existing LinkedIn headline reviewed. Check a LinkedIn headline: length against the 220-character limit, what shows in search results before the cut, whether it leads with a searchable job title, and buzzwords or vague claims to replace.
| Argument | Type | Description |
|---|---|---|
| role | string | Optional. The job title the user wants to be found for. |
| focus | string | Optional. Their specialty or industry. |
| skills | string | Optional. Main skills, comma separated. |
| headline* | string | The headline as it reads now. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"headline"
],
"properties": {
"role": {
"type": "string",
"maxLength": 200,
"description": "Optional. The job title the user wants to be found for."
},
"focus": {
"type": "string",
"maxLength": 200,
"description": "Optional. Their specialty or industry."
},
"skills": {
"type": "string",
"maxLength": 200,
"description": "Optional. Main skills, comma separated."
},
"headline": {
"type": "string",
"maxLength": 400,
"minLength": 1,
"description": "The headline as it reads now."
}
}
}Use this when the user shares a resume (pasted text or a file's text) and wants it checked, scored, reviewed for ATS problems, or wants to know what to fix. Score a resume from 0 to 100 with ATSPrep's fixed rules and list each issue with a stable code, where it is and how to fix it. Also reports how the text parsed (roles, experience and project bullets, education, skills and skill groups, input and scored word counts, with definitions). Role-specific advice, such as seniority signals, is given only when the resume names a target title or you pass target_role or job_description; with job_description the score becomes the fit for that job (0.5 requirements met, 0.3 evidence, 0.2 readability, capped for missing hard requirements or impossible claims) and it also returns job_fit and a keyword match summary. Resume up to 30,000 characters. Rules version 2026-10-23.5.
| Argument | Type | Description |
|---|---|---|
| resume_text* | string | The whole resume as plain text, one heading, role or bullet per line. |
| target_role | string | Optional. The job title the candidate is applying for. |
| job_description | string | The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"resume_text"
],
"properties": {
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
},
"target_role": {
"type": "string",
"maxLength": 120,
"description": "Optional. The job title the candidate is applying for."
},
"job_description": {
"type": "string",
"maxLength": 20000,
"minLength": 120,
"description": "The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first."
}
}
}Use this when the user wants a cover letter for a job. Draft a cover letter from the user's resume and the job posting with fixed rules: name, contact details and up to two results from the resume, the job title and top keywords from the posting. Facts that are missing show as [square-bracket] gaps for the user to fill, never as stand-ins. Returns the letter, the gaps and a checklist.
| Argument | Type | Description |
|---|---|---|
| why | string | Optional. Why this company, in the user's words. |
| name | string | Optional. Overrides the name read from the resume. |
| role | string | Optional. The job title they are applying for. |
| string | Optional. | |
| phone | string | Optional. |
| style | string | classic (default), direct, or career-change. |
| company | string | Optional. The company they are applying to. |
| results | string | Optional. One or two real results, one per line. |
| resume_text |
Use this when the user wants to resign and needs a resignation letter or their last working day. Draft a short, professional resignation letter and work out the last working day from the notice period. Missing facts show as [square-bracket] gaps. Returns the letter, the last day and a checklist (notice stated, no complaints, length).
| Argument | Type | Description |
|---|---|---|
| date | string | Optional. The day the letter is handed in, YYYY-MM-DD. Default today (UTC). |
| name | string | Optional. The user's name. |
| role | string | Optional. Their job title. |
| tone | string | formal (default), warm or short. |
| notice | string | Notice period: 1w, 2w (default) or 4w. Use notice_days for anything else. |
| reason | string | Optional. A one-line reason; none (default) gives no reason. |
| thanks | string | Optional. Something specific to thank them for. |
| company | string | Optional. |
| manager |
Use this when the user gives a job posting link instead of its text; then pass the result to the job tools. Read a public job posting from its link and return the title, company, location and full description as plain text, ready for match_job, tailor_resume, keyword_scan or interview_questions. Reads LinkedIn, Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Workday and most company careers pages. Some sites block reading; then ask the user to paste the text.
| Argument | Type | Description |
|---|---|---|
| url* | string | The job posting's public link (https). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"maxLength": 2000,
"description": "The job posting's public link (https)."
}
}
}Use this when the user wants new LinkedIn headline ideas. Write LinkedIn headline options from the user's answers, each in a proven pattern (title and focus, title and result, title and who you help…), with its length and roughly what shows in search before the cut. Uses only the answers given.
| Argument | Type | Description |
|---|---|---|
| next | string | Optional. What they want next, e.g. "open to product roles in London". |
| role* | string | The job title the user wants to be found for. |
| focus | string | Optional. Their specialty or industry, e.g. "B2B SaaS onboarding". |
| years | string | Optional. Years of experience, as a number. |
| skills | string | Optional. Main skills, comma separated. |
| results | string | Optional. One or two real results, one per line, with the numbers the user gave. |
| audience | string | Optional. Who they help, e.g. "early-stage startups". |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"role"
],
"properties": {
"next": {
"type": "string",
"maxLength": 200,
"description": "Optional. What they want next, e.g. \"open to product roles in London\"."
},
"role": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The job title the user wants to be found for."
},
"focus": {
"type": "string",
"maxLength": 200,
"description": "Optional. Their specialty or industry, e.g. \"B2B SaaS onboarding\"."
},
"years": {
"type": "string",
"maxLength": 20,
"description": "Optional. Years of experience, as a number."
},
"skills": {
"type": "string",
"maxLength": 200,
"description": "Optional. Main skills, comma separated."
},
"results": {
"type": "string",
"maxLength": 600,
"description": "Optional. One or two real results, one per line, with the numbers the user gave."
},
"audience": {
"type": "string",
"maxLength": 200,
"description": "Optional. Who they help, e.g. \"early-stage startups\"."
}
}
}Use this when the user wants one resume bullet rewritten or made stronger. Check one resume bullet with the fixed rules (score, verdict, fixes) and suggest up to three stronger rewrites that keep every fact as given. ask_user names the one fact to ask the user for; never invent it. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why.
| Argument | Type | Description |
|---|---|---|
| role | string | Optional. The job title this bullet sits under. |
| bullet* | string | One resume bullet. |
| company | string | Optional. The employer this bullet sits under. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"bullet"
],
"properties": {
"role": {
"type": "string",
"maxLength": 200,
"description": "Optional. The job title this bullet sits under."
},
"bullet": {
"type": "string",
"maxLength": 600,
"minLength": 1,
"description": "One resume bullet."
},
"company": {
"type": "string",
"maxLength": 200,
"description": "Optional. The employer this bullet sits under."
}
}
}Use this when the user is preparing for an interview and wants likely questions, for a specific job or in general. Interview questions to practise, each with what the interviewer is listening for, plus STAR answer tips. With a job_description, questions come from its skills and duties, along with what to research and questions to ask; with resume_text, from the user's own roles. Rule-based.
| Argument | Type | Description |
|---|---|---|
| kind | string | Optional. One group: posting, resume, about, behavioural, role or closing. Default all. |
| limit | integer | How many questions. Default 12. |
| resume_text | string | The whole resume as plain text, one heading, role or bullet per line. |
| job_description | string | Optional. The job posting as plain text. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"kind": {
"enum": [
"all",
"posting",
"resume",
"about",
"behavioural",
"role",
"closing"
],
"type": "string",
"description": "Optional. One group: posting, resume, about, behavioural, role or closing. Default all."
},
"limit": {
"type": "integer",
"maximum": 40,
"minimum": 1,
"description": "How many questions. Default 12."
},
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
},
"job_description": {
"type": "string",
"maxLength": 20000,
"description": "Optional. The job posting as plain text."
}
}
}Use this when the user has only a job posting (no resume yet) and wants its key skills and keywords. List the skills, tools and requirements a job posting asks for, ranked by how hard it leans on each (repetition, position, required or preferred headings), with the high-priority ones flagged. Use match_job to see which a resume already shows. Posting 120–20,000 characters. Rules version 2026-10-23.5.
| Argument | Type | Description |
|---|---|---|
| job_description* | string | The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"job_description"
],
"properties": {
"job_description": {
"type": "string",
"maxLength": 20000,
"minLength": 120,
"description": "The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first."
}
}
}Use this when the user asks for resume templates, designs or example resumes for a role. List ATSPrep's resume designs, each with a link that opens Studio in that design, and the example resumes by role, each with a link that opens it in Studio and a preview image.
No arguments.
{
"type": "object",
"properties": {}
}Use this when the user has a resume and a job posting and asks how well they match, what keywords are missing, or whether to apply. For rewrites, use tailor_resume instead. Compare a resume with a job posting: the posting's keywords found in the resume (with how they matched: exact, normalized, alias or stem, and the matched span), the ones missing with the posting sentence they come from, each term's weight and whether the posting lists it as required or preferred, and weighted overall, required and preferred coverage. Posting 120–20,000 characters. Rules version 2026-10-23.5.
| Argument | Type | Description |
|---|---|---|
| resume_text* | string | The whole resume as plain text, one heading, role or bullet per line. |
| job_description* | string | The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"resume_text",
"job_description"
],
"properties": {
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
},
"job_description": {
"type": "string",
"maxLength": 20000,
"minLength": 120,
"description": "The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first."
}
}
}Use this when the user wants to edit their resume in an editor, apply a template, or download it as a PDF or Word file. Make a link that opens this resume in ATSPrep Studio, the free editor, so the user can fix it, pick a template and download a PDF. The text travels in the link's #fragment, which is never sent to a server.
| Argument | Type | Description |
|---|---|---|
| resume_text* | string | The whole resume as plain text, one heading, role or bullet per line. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"resume_text"
],
"properties": {
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
}
}
}Use this when the user gives an answer to an interview question and wants feedback on it. Review the user's answer to an interview question: a rating, length and speaking time, STAR coverage for stories, filler words, specific checks, the follow-up an interviewer would likely ask, and a stronger version that keeps to the user's own facts. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why.
| Argument | Type | Description |
|---|---|---|
| kind | string | story (default: a past example, scored on STAR), pitch (tell me about yourself), plan (how would you…), number (salary or a figure) or close (questions for them). |
| answer* | string | The user's answer, as they would say it. |
| question* | string | The interview question. |
| resume_text | string | Optional. The resume, so the stronger answer can use real facts from it. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"question",
"answer"
],
"properties": {
"kind": {
"enum": [
"story",
"pitch",
"plan",
"number",
"close"
],
"type": "string",
"description": "story (default: a past example, scored on STAR), pitch (tell me about yourself), plan (how would you…), number (salary or a figure) or close (questions for them)."
},
"answer": {
"type": "string",
"maxLength": 4000,
"minLength": 1,
"description": "The user's answer, as they would say it."
},
"question": {
"type": "string",
"maxLength": 400,
"minLength": 1,
"description": "The interview question."
},
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "Optional. The resume, so the stronger answer can use real facts from it."
}
}
}Use this when the user wants their resume rewritten or tailored for a specific job posting. Tailor a resume to a job posting: the posting's keywords the resume is missing (from match_job's rules) and suggested rewrites of the user's own summary and bullets that bring in the posting's terms only where the existing line already supports them. Each suggestion lists the posting terms it borrowed and confirm_with_user lists terms to ask about, never to add unasked. End the reply with next_step: the link that opens the resume in ATSPrep to check the edits and download. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why.
| Argument | Type | Description |
|---|---|---|
| resume_text* | string | The whole resume as plain text, one heading, role or bullet per line. |
| job_description* | string | The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"resume_text",
"job_description"
],
"properties": {
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
},
"job_description": {
"type": "string",
"maxLength": 20000,
"minLength": 120,
"description": "The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first."
}
}
}Use this when the user wants a resume summary or professional profile written from their resume. Draft professional summaries from a resume: rule-based drafts built from its title, skills and the bullets that carry a figure, plus AI drafts that use only facts in the resume. Part of the answer is drafted by an AI model (Gemma 4, with Llama 3.3 70B as a backup, on Cloudflare Workers AI) behind ATSPrep's guard, which drops any figure, name or tool the user's text doesn't contain. If the AI part is unavailable, the rule-based part still comes back and ai.message says why.
| Argument | Type | Description |
|---|---|---|
| resume_text* | string | The whole resume as plain text, one heading, role or bullet per line. |
| target_title | string | Optional. The job title the summary should aim at. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"resume_text"
],
"properties": {
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
},
"target_title": {
"type": "string",
"maxLength": 200,
"description": "Optional. The job title the summary should aim at."
}
}
}| string |
| The whole resume as plain text, one heading, role or bullet per line. |
| current_title | string | Optional. The user's current or last job title. |
| hiring_manager | string | Optional. The hiring manager's name, if known. |
| job_description | string | The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"why": {
"type": "string",
"maxLength": 600,
"description": "Optional. Why this company, in the user's words."
},
"name": {
"type": "string",
"maxLength": 200,
"description": "Optional. Overrides the name read from the resume."
},
"role": {
"type": "string",
"maxLength": 200,
"description": "Optional. The job title they are applying for."
},
"email": {
"type": "string",
"maxLength": 200,
"description": "Optional."
},
"phone": {
"type": "string",
"maxLength": 200,
"description": "Optional."
},
"style": {
"enum": [
"classic",
"direct",
"career-change"
],
"type": "string",
"description": "classic (default), direct, or career-change."
},
"company": {
"type": "string",
"maxLength": 200,
"description": "Optional. The company they are applying to."
},
"results": {
"type": "string",
"maxLength": 600,
"description": "Optional. One or two real results, one per line."
},
"resume_text": {
"type": "string",
"maxLength": 30000,
"description": "The whole resume as plain text, one heading, role or bullet per line."
},
"current_title": {
"type": "string",
"maxLength": 200,
"description": "Optional. The user's current or last job title."
},
"hiring_manager": {
"type": "string",
"maxLength": 200,
"description": "Optional. The hiring manager's name, if known."
},
"job_description": {
"type": "string",
"maxLength": 20000,
"minLength": 120,
"description": "The full job posting as plain text, including its requirements (120–20,000 characters). For a link, call fetch_job_post first."
}
}
}| string |
| Optional. Their manager's name. |
| notice_days | integer | Optional. A notice period in days, instead of notice. |
| offer_handover | boolean | Offer to help hand over. Default true. |
| working_days_only | boolean | Count notice in working days (Monday to Friday). Default false: calendar days. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Optional. The day the letter is handed in, YYYY-MM-DD. Default today (UTC)."
},
"name": {
"type": "string",
"maxLength": 200,
"description": "Optional. The user's name."
},
"role": {
"type": "string",
"maxLength": 200,
"description": "Optional. Their job title."
},
"tone": {
"enum": [
"formal",
"warm",
"short"
],
"type": "string",
"description": "formal (default), warm or short."
},
"notice": {
"enum": [
"1w",
"2w",
"4w"
],
"type": "string",
"description": "Notice period: 1w, 2w (default) or 4w. Use notice_days for anything else."
},
"reason": {
"enum": [
"none",
"new-role",
"relocation",
"study"
],
"type": "string",
"description": "Optional. A one-line reason; none (default) gives no reason."
},
"thanks": {
"type": "string",
"maxLength": 600,
"description": "Optional. Something specific to thank them for."
},
"company": {
"type": "string",
"maxLength": 200,
"description": "Optional."
},
"manager": {
"type": "string",
"maxLength": 200,
"description": "Optional. Their manager's name."
},
"notice_days": {
"type": "integer",
"maximum": 180,
"minimum": 1,
"description": "Optional. A notice period in days, instead of notice."
},
"offer_handover": {
"type": "boolean",
"description": "Offer to help hand over. Default true."
},
"working_days_only": {
"type": "boolean",
"description": "Count notice in working days (Monday to Friday). Default false: calendar days."
}
}
}