Reference
Tools reference
These are the 14 tools your assistant sees once it’s connected, with the description it is given for each. You never call them yourself, but knowing them helps you ask for the right thing. The access column is the permission each one needs.
| Tool | What it does | Access |
|---|---|---|
get_account | Account and plan. Who is signed in, their plan, and how much of each monthly allowance is left. | read |
list_resumes | List resumes. The user's saved resumes, newest saved first. Each has an id for the other tools and an editorUrl for changes an agent cannot make. Drafts and the unsaved working copy are never listed. | read |
get_resume | Read a resume. One saved resume as text, for reading or for tailoring elsewhere. Returns the saved document, never the unsaved working copy, and its editorUrl, where the user can change it in OpenRoles. | read |
list_applications | List tracked applications. The tracker: every application with its current stage, whether the company has replied, days waiting, which resume was sent, and the next action. Includes the summary (funnel, reply rate) and the follow-up nudges the product would show. | read |
get_application | Read one application. One application in full: the posting text, the match checklist as it stood when it was sent, the resume used, and the whole event history — who moved it to which stage, when, and from where (manual, extension, email, agent). | read |
get_saved_answers | Saved application answers. The answers a resume never holds — current and expected CTC, notice period, work authorisation and the rest — exactly as the user saved them for application forms. Null where they have not answered. | read |
list_jobs | List open jobs. Open engineer, product manager and designer roles in India from the OpenRoles job timeline, newest first. Each has a jobUrl — send the user there to apply with OpenRoles, which fills the company's form for them. | read |
log_application | Log an application. Record that the user applied, or is about to apply, for a job. Creates a tracker row. If a row already exists for the same company and role, it is updated rather than duplicated. | write |
update_application | Update an application. Move an application to a stage, record that the user followed up, set or clear the next action, or say which resume was sent. Appends to the event history; nothing is overwritten. | write |
delete_application | Delete an application. Remove an application and its history. Cannot be undone. | write |
upload_resume | Upload a resume. Save a resume you have written as a new version in OpenRoles, so the user can send it, the Chrome extension can fill forms from it, and the tracker can record it against applications. Send the document as structured fields — the schema is the input. Give it a name the user will recognise in a list ('Razorpay — Backend SDE'). If it is a tailored take on an existing resume, pass that resume's id as parentResumeId so it joins that family instead of counting as a new base resume. If it was written for one posting, pass forJobUrl so the extension offers it on that page. OpenRoles does not fact-check what you upload: it is saved as the user's own words, so everything in it must come from them. | write |
update_resume | Rename or archive a resume. Rename a resume version, or archive it so it stops appearing in lists (or unarchive it). Archiving never deletes: an application that was sent with it still points at it. | write |
set_saved_answer | Save an application answer. Save one of the fixed application-form answers (current CTC, notice period, …) in the user's own words, for the extension to reuse. Only the listed keys exist; nothing else can be stored. | write |
score_resume | Score a resume. Run OpenRoles' resume score on a saved resume. Returns the score, the six-criterion breakdown and the specific problems found. | ai |
When a request is refused, for example because your pass has ended, the tool returns a plain sentence your assistant can read to you, with a link to pricing.