Create or edit a role
editJobCreate and edit the company's roles. create: one of position (blank role), jobUrl (posting link) or jobText (pasted JD). Returns the jobId. Only when the user explicitly asks for a new role. Then run get, name the missing fields and hand over the getDashboardLink role_preview link. update: jobId + updates. Only provided fields change. lifecycle open publishes the role and starts matching, which needs employmentType, a salary bound and an experience bound. set_brief: jobId + brief. Markdown sourcing brief for Clera's matching team, never shown to candidates; full replace, null clears. set_roles: jobId + roles. 1 to 3 job-category tags, required for matching; the roles field says which tags belong. set_stages: jobId + stages. Ordered interview stages, full replace, matched by name. A stage with candidates on it can't be removed or renamed here; hand over the getDashboardLink role_preview link instead of retrying. add_requirements: jobId + requirements. Discrete, evaluable criteria the contact stated, e.g. "must have payments experience". Appends; vague preferences go to update_memory. update_memory: jobId + memoryUpdates. Record a note the moment the contact says something durable about this role, without being asked. Null deletes a key. create_question: jobId + question and optional fields. Returns the full list. update_question: jobId + questionId + fields to change. Returns the full list. delete_question: jobId + questionId. Returns the full list. set_requirements: jobId + requirements. Full replace; omitted requirements are removed. Returns the list. add_location: jobId + normalizedLocation, e.g. 'Berlin, Germany', geocoded strictly; reformulate if rejected. add_remote_location: jobId + code. 'worldwide', a region or country slug, for remote roles. remove_location: jobId + locationId. Returns the full list with ids. Ids come from readJob (list, list_questions, list_locations) or from create.
Clera privately records this tool's inputs and results for usage tracking and support.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"command": "<command>"
},
"name": "editJob"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | add_remote_location (required): a canonical remote code: 'worldwide' for anywhere, a region slug (e.g. 'eu', 'north-america'), or a country slug (e.g. 'germany', 'united-states'). Use this for remote roles instead of geocoding a city. | |
| brief | No | set_brief (required): the full job brief as structured markdown with ## sections like Ideal Profile, Must-Haves, Nice-to-Haves, Red Flags, Green Flags, Target Companies, Compensation, Interview Process. Replaces the entire brief. Pass null to clear the brief entirely. | |
| jobId | No | Every command except list and create (required): the job's UUID. Resolve it with list. | |
| orgId | No | Organization to act as. Only needed when you belong to more than one organization. | |
| roles | No | set_roles (required): 1 to 3 job-category tags from Clera's role list for the work this hire does day to day, e.g. ["AE", "Sales"] for a closing sales role. A name not on the list is refused with the list. Synonyms of that category count; adjacent categories do not: a sales role never gets Business Development, Growth or Account Manager. Every tag widens candidate search, so an extra tag pulls in people from that other category. | |
| jobUrl | No | create (one of position, jobUrl, jobText): a careers-page or job-posting link. The server scrapes it, parses the posting into a full role, and detects duplicates. | |
| stages | No | set_stages (required): ordered list of interview stages, full replace, priority follows array order. Stages are matched by name, so a rename reads as a removal plus an insert. Moving candidates off a stage is done on the dashboard, where the company picks their new stage. | |
| command | Yes | Which operation to run: create | update | set_brief | set_roles | set_stages | add_requirements | update_memory | create_question | update_question | delete_question | set_requirements | add_location | add_remote_location | remove_location. The tool description explains each. | |
| jobText | No | create (one of position, jobUrl, jobText): the full pasted job description text. The server parses it into a full role. | |
| updates | No | update (required): the role fields to change, only provided fields are written. Includes the candidate-facing description, lifecycle, pay (base salary and OTE), experience, visa, workplace, hiringManagerContactId, calendarLink, applicationFormUrl and goodFitLinkedinUrls. | |
| optional | No | create_question, update_question (optional): whether the candidate may skip this question. | |
| position | No | create (one of position, jobUrl, jobText): job title, e.g. 'Senior Backend Engineer'. Use this to start a blank role you fill in yourself. | |
| priority | No | create_question, update_question (optional): display order, lower shows first. | |
| question | No | create_question (required), update_question (optional): the question text shown to the candidate. | |
| lifecycle | No | list (optional): only roles in this lifecycle. create (optional, default draft): set 'open' when the role details are ready for sourcing. | |
| locationId | No | remove_location (required): the location's id from list_locations. | |
| questionId | No | update_question, delete_question (required): the screening question's id, from list_questions. | |
| description | No | create (optional): initial job description. Only meaningful with position; a jobUrl/jobText create derives the description from the parsed posting. Markdown: ## per section, - per list item, blank line between paragraphs. Keep posting's sections + wording. | |
| explanation | No | create_question, update_question (optional): why the question is asked. Pass null to clear it. | |
| questionType | No | create_question, update_question (optional): answer input type. Defaults to TEXTAREA when omitted. | |
| requirements | No | add_requirements (required): requirements to add, each becomes a separate row in the dashboard | |
| memoryUpdates | No | update_memory (required): memory entries to upsert, a null value deletes the key | |
| normalizedLocation | No | add_location (required): a physical place as free text, e.g. 'Berlin, Germany'. The server geocodes it and rejects input that resolves to no place. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | No | ||
| jobs | No | ||
| brief | No | ||
| jobId | No | ||
| stages | No | ||
| command | Yes | ||
| entries | No | ||
| message | Yes | ||
| diffBlock | No | ||
| locations | No | ||
| questions | No | ||
| stageCount | No | ||
| requirements | No | ||
| assignedRoles | No | ||
| fieldsUpdated | No | ||
| alreadyExisted | No |