Ashby API

Add a tag to a candidate in the recruitment system. Use this tool to attach a specific tag to a candidate in the Ashby recruitment platform, which helps in categorizing and managing candidates efficiently. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add a candidate to a specified project. Use this tool to assign a candidate to a specific project. Requires appropriate permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Adds a completed assessment to a candidate's record. Use this tool to update a candidate's profile with a completed assessment. Requires the 'candidatesWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add a user to the hiring team for an application. This tool adds an Ashby user to the hiring team at the application level. Requires candidateWrite permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Adds a job to an opening. Use this tool to add a job to an existing opening. Requires the `jobsWrite` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Adds a location to a job opening. Use this tool to associate a specific location with a job opening. Requires appropriate permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add a user to an interviewer pool in Ashby. This tool allows you to add a user to an interviewer pool using the Ashby API. Ensure you have the necessary permissions before making the call. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Permanently anonymize a candidate's data in the system. Use this tool to anonymize a candidate's data. Ensure all candidate applications are archived or marked as hired before calling this tool. This action is irreversible and requires 'candidatesWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Archive a department within an organization. Use this tool to archive a specified department within an organization. Ensure you have the necessary permissions before calling this tool. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Archive an interviewer pool when needed. Use this tool to archive an interviewer pool, typically when it's no longer needed or active. Ensure you have the necessary permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Archives a location or location hierarchy. Use this tool to archive a specific location or an entire location hierarchy when needed. It requires permission to modify organization data. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for an Ashby user by email address. This tool is used to find and retrieve details of an Ashby user by providing their email address. It requires the `organizationRead` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Cancel an ongoing assessment. This tool is used to cancel an ongoing assessment. Call this tool when you need to stop a scheduled or active assessment. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Cancel an interview schedule by ID. Use this tool to cancel an interview schedule by its unique identifier. Requires appropriate permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Change the source of a job application. Use this tool to change the source of a job application. Requires the 'candidatesWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new candidate entry. Use this tool to create a new candidate in the system. Requires permissions to write candidates. For setting custom field values, use the custom fields endpoint. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add a note to a candidate's profile in Ashby. This tool allows for the creation of a note on a candidate's profile, supporting HTML formatted text. It's useful for recruiters and interviewers to document additional information or insights about a candidate. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Initiate a new offer version for a candidate. Used to create and return an offer version instance for a candidate's in-progress offer process. This instance can then be filled out and submitted using the `offer.create` endpoint. Requires the `offersWrite` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a candidate referral in the system. Use this tool to create a referral for a candidate, typically when hiring or recommending someone for a position. Requires the `candidatesWrite` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new candidate tag in the Ashby system. Use this tool to create a new tag for candidates in the Ashby system, requiring the 'hiringProcessMetadataWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a new custom field in Ashby. Use this tool to create a new custom field in Ashby, granted the necessary permissions are available. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new department within an organization. This tool is used to create a new department in an organization. It requires appropriate permissions and should be called when a user needs to add a new department to their organization in the Ashby system. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a new interviewer pool for hiring processes. Use this tool to create an interviewer pool, which is a group of interviewers assigned for conducting interviews in a hiring process. Requires appropriate permissions to execute. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new scheduled interview in Ashby. This tool creates a scheduled interview in the Ashby platform, requiring the 'interviewsWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a job application for a candidate. Use this tool to create a job application for a candidate when sourcing for a job posting. Ensure you have the 'candidatesWrite' permission. This tool is not for job boards; refer to 'applicationForm.submit' for that purpose. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new job opening in the system. Use this tool to create a new job opening. Requires 'jobsWrite' permission. For setting custom fields, use the 'customFields.setValue' endpoint.

Create a location or location hierarchy. This tool creates a new location or a location hierarchy within the system. It is useful for adding organizational locations, such as branches or divisions. Requires organizationWrite permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new job listing with specified details. Use this tool to create a new job listing. It requires permission to write jobs and can be used in conjunction with the custom fields setting tool to add additional job details. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new offer using specified form fields. This tool is used to create a new offer by filling out various form fields. It requires the 'offersWrite' permission and supports field types such as Boolean, Currency, Date, Number, String, ValueSelect, and MultiValueSelect. Each field must be filled out with the accepted value type as per the specification. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a survey request and get a survey URL. Use this tool to create a survey request for candidates and obtain a URL which can be shared with them to complete the survey. Note that this tool does not send the survey URL to the candidate automatically; it just generates the link. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new survey submission. This tool creates a new survey submission and should be called when you need to record a survey response. Requires appropriate permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a new webhook setting in Ashby. This tool creates a webhook setting in Ashby. It should be called when you need to set up a new webhook to receive event notifications. Ensure the necessary permissions are granted. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Deletes a specified webhook setting. Use this tool to delete an existing webhook setting when no longer needed, ensuring the user has the required permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Fetch application details using application or form instance ID. Use this tool to retrieve details of an application by providing either the application ID or the submitted form instance ID. If both are provided, the application ID is prioritized. Requires 'candidatesRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Fetch interview stage details by ID. Use this tool to obtain detailed information about a specific interview stage by its ID. Requires the 'interviewsRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for candidates by email or name. Use this tool to find candidates based on email and/or name for operations requiring a focused candidate set. Useful for building candidate autocompletes. Ensure you have the required permissions.

Generate a new report or poll status of report generation. This tool generates a new report or checks the status of an existing report generation process in a two-step manner. Initially, call with a reportId to start report generation and receive a requestId. Then, poll using both reportId and requestId until the report's status is complete or failed. Ideal for asynchronous report operations that exceed 30 seconds. Requires `reportsRead` permission. If rate limits are exceeded, consider using the synchronous endpoint. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve information about the current API key. This tool retrieves details about the API key being used for requests. It requires the 'apiKeysRead' permission and is essential for verifying or monitoring API key usage and access.

Fetch a paginated list of application history items. Use this tool to obtain detailed history records of an application, including updates and changes over time. Useful for tracking application progress or changes in candidate information. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all approvals in the organization. This tool retrieves all approvals within the organization. It can optionally filter results by entity type and entity ID. Ensure the 'approvalsRead' permission is available when using this tool. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information of a specific Ashby user. Use this tool to get detailed information about a specific user in Ashby by their user ID. Requires the 'organizationRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all users in Ashby and their access levels. Call this tool to get a list of all users in Ashby, including their global roles which indicate their access levels. Useful for understanding user permissions and roles within an organization on Ashby. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve AI evaluations for candidate job criteria. Fetch AI-generated evaluations assessing how well a candidate meets job requirements, including outcome and reasoning details. Requires specific permissions and enabled features. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information of a candidate using their ID. This tool retrieves comprehensive information about a candidate based on their unique ID, ensuring the caller has the necessary permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve information about a custom field. Get details about a custom field, requiring the 'hiringProcessMetadataRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Fetch department details by ID. Use this tool to retrieve detailed information about a department by providing its ID. It's useful for getting specifics on organization departments. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Fetch detailed information about a specific feedback form by ID. Use this tool to retrieve information about a single feedback form based on its ID, useful for understanding the content and structure of the feedback form. Ensure the necessary permissions are in place. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all available hiring team roles for applications. This tool fetches all available roles within the hiring team for applications in the organization. Requires candidatesRead permission.

Retrieve detailed information about a specific interview. This tool is used to fetch interview details using a specific interview ID from the Ashby service. It requires the `interviewsRead` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve information about an interviewer pool. Use this tool to get details about an interviewer pool from Ashby. Requires the 'hiringProcessMetadataRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve interviewer settings for a user. This tool retrieves the interviewer settings for a specified user in the organization. It requires the 'organizationRead' permission to access user information. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all interview schedules for the organization. This tool is used to obtain a list of all interview schedules within an organization. It is ideal for managing or reviewing interview timelines and requires the 'interviewsRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information about a job using its ID. This tool provides comprehensive details about a specific job when given the job ID. It should be used when there's a need to gather information about job specifics, such as title, description, and requirements. Requires appropriate permissions to access job data. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information about a specific job posting. This tool retrieves comprehensive details about a specific job posting, including data for rich search results and application form definitions. It is useful for accessing detailed job information to present on websites or applications. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve the latest version of all offers available. Use this tool to get a list of all offers with their latest version from Ashby. Requires offersRead permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information for a specific location. Use this tool to obtain detailed information about a specific location by its ID. This requires the organizationRead permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve details about a specific offer using its ID. Use this tool to obtain detailed information about a specific offer by providing its ID. Requires the necessary permission to access the offer details. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve job opening details using a UUID. Call this tool to get specific information about a job opening identified by its UUID. Useful for accessing job details when the UUID is known and the `jobsRead` permission is granted. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information about a project. This tool retrieves detailed information about a project using its UUID. It requires the 'jobsRead' permission. Use it to access comprehensive project data when given a valid UUID. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Fetches or creates the default referral form details. Use this tool to obtain the default referral form information. If no form exists, a default one will be created. Ensure that the 'hiringProcessMetadataRead' permission is granted.

Retrieve details of a survey form definition by id. Use this tool to get details about a specific survey form definition using its id. Requires the hiringProcessMetadataRead permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Adds a user to the hiring team for a job or application. This tool is used to add an Ashby user to a hiring team at the application, job, or opening level. It requires the `organizationWrite` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a job's interview plan details. Fetches the interview plan for a specific job, detailing the activities and interviews required at each stage. Useful for understanding the scheduling needs and process of a job interview. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all open, closed, and archived jobs from Ashby. This tool is used to list all jobs, including open, closed, and archived ones. It can also include draft jobs if specified in the status parameter. Useful for accessing comprehensive job listings efficiently. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all available locations. Use this tool to obtain a complete list of locations, excluding regions. Ensure you have the 'organizationRead' permission to access this data. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all sources for hiring processes. Use this tool to obtain a comprehensive list of sources related to hiring processes. It requires the 'hiringProcessMetadataRead' permission to access the data.

Retrieve interview feedback and scorecards for applications. This tool retrieves all interview scorecards and feedback submissions associated with a specific application, including form structure, submitted responses, and interview context. Useful for assessing candidate performance through submitted feedback. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all applications in the organization. Use this tool to get a comprehensive list of all candidate applications within your organization. Requires 'candidatesRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of archive reasons. Use this tool to get a list of reasons for archiving within the Ashby service. Requires the 'hiringProcessMetadataRead' permission.

Retrieve a list of available assessments. This tool calls the partner's API to list all assessments supported by them. It is used to obtain the current assessment offerings.

Retrieve client info records for a candidate. Use this tool to list all client information records for a specific candidate. Requires candidatesRead permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all notes associated with a candidate. Use this tool to retrieve all notes related to a specific candidate. This is useful for reviewing feedback or comments made during the recruitment process. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all projects linked to a candidate. Use this tool to list all projects associated with a specific candidate. Requires appropriate permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all candidates in an organization. Use this tool to get a comprehensive list of all candidates within your organization. Useful for accessing candidate data for recruitment or management purposes. Requires 'candidatesRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all candidate tags. Use this tool to get a comprehensive list of candidate tags. Requires the hiringProcessMetadataRead permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Get a list of close reasons for jobs or openings. Use this tool to retrieve all the reasons for closing jobs or openings. Useful for understanding job status changes. Requires hiring process metadata read permissions.

Retrieve a list of all custom fields. Use this tool to get a list of all custom fields available in the system. This action requires the 'hiringProcessMetadataRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all departments. Use this tool to get a complete list of all departments within the organization. Requires appropriate permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all enabled communication templates. Use this tool to retrieve a list of all enabled communication templates in the system. Useful for managing or viewing templates that are currently active.

Retrieve a list of all enabled job boards. Use this tool to get information on currently enabled job boards. Ideal for understanding which job boards are active and available for use.

Retrieve a list of all feedback forms. Call this tool to obtain a list of all feedback forms. Requires 'hiringProcessMetadataRead' permission for access. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve possible hiring team roles within an organization. Call this tool to get a list of hiring team roles for an organization. Useful for understanding the roles involved in hiring processes. Ensure you have the 'organizationRead' permission to use this tool.

Fetches a list of all interviewer pools. Use this tool to retrieve a complete list of interviewer pools. It requires the `hiringProcessMetadataRead` permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of interview events for a schedule. Use this tool to obtain a list of interview events linked to a specified interview schedule. It requires the necessary read permissions for accessing interview data. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Fetch a list of all available interview plans. Use this tool to retrieve a list of all interview plans from Ashby. Ideal for obtaining current interview structures and details. Ensure the `interviewsRead` permission is granted before use. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all scheduled interviews. Use this tool to get a comprehensive list of all interviews. This is useful for checking scheduled, completed, or upcoming interviews. Ensure you have the required permissions to access this information. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all interview group stages in order. Use this tool to list all the interview group stages for a specific interview plan. This operation requires the 'interviewsRead' permission.

Retrieve all interview stages for an interview plan in order. Use to obtain a list of all interview stages for a specific interview plan, ensuring they are in the correct order. Useful for understanding the interview process structure. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of current job openings. Used to fetch a list of available job openings from the Ashby platform. Requires the 'jobsRead' permission to access opening list information.

Retrieve all active and inactive job templates. Use this tool to obtain a list of all job templates, both active and inactive. Useful for managing and reviewing job templates. Requires 'jobsRead' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of projects. Use this tool to obtain a list of projects. Requires the 'candidatesRead' permission.

Retrieve all published and publicly listed job postings. Use this tool to get a list of job postings that are published and set for public display. Ensure to set the `listedOnly` parameter to `true` to avoid exposing unlisted jobs. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all source custom tracking links. Fetches a list of all custom tracking links used for source tracking, requiring the 'hiringProcessMetadataRead' permission.

Retrieve all survey form definitions. Fetches a list of all available survey form definitions. Useful for obtaining the structure and details of surveys used in the hiring process. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of all survey requests. Call this tool to get an overview of all survey requests currently listed. Useful for accessing details on candidate surveys when you have the necessary permissions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all survey submissions for a specific type. Use this tool to obtain a list of all survey submissions associated with a particular survey type. Useful for analyzing survey results or monitoring participation. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Relocate a department to a new parent structure. This tool is used to move a department to a different parent structure within an organization. Requires appropriate permissions to execute. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Move a location within the organizational hierarchy. This tool is used to move a location in the location hierarchy. It requires the organizationWrite permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Approve an offer or a specific step in the approval process. This tool approves an entire offer or a specific step within an offer's approval process. Use it to mimic the "Force Approve" function in Ashby, requiring the `offersWrite` permission. Call without `approvalStepId` and `userId` to approve the whole process, or provide both to approve a specific step. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Remove a user from the hiring team at the application level. This tool removes an Ashby user from the hiring team for a specific application. It requires the `candidateWrite` permission to perform the action. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Remove a job from an opening. Use this tool to remove a job from an opening. This action requires the 'jobsWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Remove a location from a job opening. This tool is used to remove a specified location from a job opening. It requires the `jobsWrite` permission and should be called when modifying job openings to update their location details. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Remove a member from the hiring team at job or application level. This tool is used to remove an Ashby user from the hiring team for a specific application, job, or opening level. It requires the organization's write permission to perform the operation. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Remove a user from an interviewer pool. Use this tool to remove a specific user from an interviewer pool. Ensure you have the necessary permissions before making this call. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Restores an archived location or hierarchy. Use this tool to restore an archived location or location hierarchy in the system. Requires organizationWrite permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Restores a previously deleted department. Use this tool to restore a department that was previously deleted. This requires the organizationWrite permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Restores an archived interviewer pool. Use this tool to reactivate an interviewer pool that was previously archived. Ensure the necessary permissions are in place before performing this action. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve the URL of a candidate's associated file. Use this tool to retrieve the URL of a file linked to a specific candidate. Ensure you have the required 'candidatesRead' permission. Note that using Ashby demo data may cause errors; create a test candidate for testing. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve report data synchronously with Ashby. Call this tool to retrieve report data synchronously using Ashby's reportSynchronous endpoint. Use it when a quick report access is needed and is within the provided time constraints and limits. For longer or more resource-intensive reports, consider using asynchronous alternatives. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve detailed information on a specific webhook setting by ID. This tool fetches detailed information about a specified webhook setting based on its ID. It is useful for understanding configuration details and is to be used when identifying the specifics of a webhook is necessary. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for job openings by identifier. Use this tool to search for job openings by their identifier. Requires appropriate permissions to access the data. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for jobs by title. Use this tool to find job listings by specifying the job title. This is useful for locating specific job openings across various industries and locations. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for projects by title for quick lookups. This tool allows you to search for projects by their titles, returning up to 100 results. Use it when you need to quickly find a specific project or perform operations that require a small set of project results.

Update the value of a custom field for an object. Use this tool to set the value of a custom field for a specified object, requiring specific data types based on the field. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update the status of a job by its ID. This tool updates the status of a job based on its ID. It validates transitions between statuses: Drafts can be changed to Open or Archived, Open jobs to Closed, Closed jobs to Draft or Archived, and Archived jobs to Draft. It requires the 'jobsWrite' permission. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Set or unset the archived state of a job opening. Use this tool to change the archived status of a specific job opening. Useful when needing to manage the visibility or status of job opportunities in a system, requiring 'jobsWrite' permission.