jobhunt.app/mcp

Revise a cover letter with your agent

Change requested passages and preserve the rest.

Updated

Step by step

  1. Open the saved letter

    Ask your connected agent to revise an existing cover letter. It reads the current saved version and identifies whether the letter belongs to a company or a specific application. Revising the opening keeps the same letter; it does not create another copy.

  2. Keep your original source

    When bringing an existing letter into a Hunt Docs package, keep your original file or pasted text. Saving reviewed letter fields and version history does not prove that the original source was archived separately or that every correction is linked to it. The resume importer is for resumes, not cover letters. Review paragraph order, recipient and sign-off, and clear any starter wording, date or greeting you did not supply before using the letter.

  3. Identify the exact change

    Say which paragraph or detail should change. If the letter contains similar passages or the request is unclear, the agent checks with you before replacing text.

  4. Preserve the other paragraphs

    The edit replaces the selected section. The agent keeps every paragraph you did not ask to change, preserves their order and does not invent recipient, date or career facts.

  5. Review the saved revision

    Check the saved letter. If you want a PDF, prepare it again so the file reflects the new revision. Existing prepared files keep their earlier content.

  6. See the pages

    Ask your assistant to show the letter. Where your assistant shows JobHunt cards, a card shows the letter as it will print, with Before and After for the change just made, and an Open in JobHunt button. The same works for thank-you, networking and other letters, references and statements. Say "stop showing previews" if you do not want them. Page previews in the chat are rolling out with JobHunt's new assistant tools; until your assistant offers them, open the document on jobhunt.app.

What happens next

The requested letter passage is updated while the rest remains in the saved document.

Troubleshooting

If the source changed before the edit was saved, reread its current revision and review it before retrying. Unknown recipient details remain blank unless you supply them.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READget document

Read one owned resume or cover letter with revision and fact sources. Use explicit detail reads for editing; summaries intentionally omit body content.

GET /api/v1/journey/get_document

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
WRITEupdate resume section

Replace one complete document section at its current revision. Keep returned field paths and sources; only confirm user-reviewed facts. Linked contact details are edited through the package contact profile. Preserve other sections and immutable prepared PDFs.

POST /api/v1/journey/update_resume_section_v2

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →
WRITEadd package document

Add a private resume, cover letter, reference list or statement to an explicitly selected master package. Uses the browser creation rules and selected source identity; does not publish or submit. Keep request_id and account unchanged on retry.

POST /api/v1/journey/add_package_document_v2

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →
WRITEcreate document checkpoint

Save a named checkpoint of the current owned document, using its current revision. Does not change document content, existing history or prepared PDFs. Keep a stable request_id for retries.

POST /api/v1/journey/create_document_checkpoint_v2

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →
READlist document revisions

Read up to 30 saved versions from the shared website and chat history. Follow next_before_id while has_more to find older versions, including timestamp ties. Optional include_metadata returns account/document-bound names, dates, triggers and total without document bodies. expected_account_id fences a changed account. Pages are live history, not an immutable collection snapshot. A null revision means a legacy website checkpoint, not missing content. Select the user's exact version before restoring.

GET /api/v1/journey/list_document_revisions

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →