Teamtailor MCP Server
for AI Agents

Create a new answer for a candidate's response to an application question. Requires candidate_id from list_candidates, question_id from list_questions, and picked_question_id from list_picked_questions.

Retrieve candidate responses to application questions. IMPORTANT - You must use filter_question parameter to avoid timeout errors, as the answers endpoint returns massive datasets that will cause Bad Gateway errors without filtering. Only question and candidate relationships can be included.

Retrieve a specific answer by its unique identifier. Returns the complete response including the answer content and metadata. Only question and candidate relationships can be included.

Add a new candidate to the recruitment system with their profile information. Conditional requirement - either email is required OR sourced must be set to true. This creates a candidate record that can then be associated with job applications. Requires Admin scope with write permissions.

Retrieve a paginated list of all candidates in the recruitment system. Candidates are individuals who have applied for positions or been sourced by recruiters. You can filter by various criteria including email address, department, role, location, and date ranges. Available include options are activities, division, department, role, job-applications, questions, answers, locations, regions, uploads, custom-field-values, partner-results, form-answers, onboardings, and interviews. Requires Admin scope.

Retrieve complete information about a specific candidate using their unique identifier. Returns the full candidate profile including personal details, contact information, application history, and any associated documents or data. Available include options are activities, division, department, role, job-applications, questions, answers, locations, regions, uploads, custom-field-values, partner-results, form-answers, onboardings, and interviews. Requires Admin scope.

Modify an existing candidate's profile information. Use this to update contact details, correct information, or add additional data to a candidate record. Requires Admin scope with write permissions.

Permanently remove a candidate and all their associated data from the system. This action cannot be undone and should be used with caution. Requires Admin scope with elevated write permissions.

Retrieve the organization's company profile and account settings. Returns core company information including company name, career site URL, branding settings, and account configuration. This is the central resource for understanding the Teamtailor account setup.

Update the organization's company profile settings. Allows modifying company name and website. Can also update the manager relationship by providing a user ID. Requires Admin scope with write permissions.

Set a custom field value for a candidate. Requires custom_field_id from list_custom_fields (must be a Candidate owner-type field) and candidate_id from list_candidates.

Retrieve custom field values for specific candidates or jobs.

Retrieve a specific custom field value by its unique identifier. Obtain the ID from list_custom_field_values action.

Modify an existing custom field value. Requires id from list_custom_field_values or create_custom_field_value.

Create a new custom field definition for candidates or jobs.

Retrieve all custom field definitions configured in the system. Custom fields extend the standard candidate and job data model with additional attributes specific to your organization's needs, such as source tracking, skill ratings, or compliance information. Requires Admin scope.

Retrieve a specific custom field definition by its unique identifier. Requires id obtained from list_custom_fields.

Update an existing custom field definition. Requires id from list_custom_fields. Note that api-name cannot be changed after creation.

Create a new select-type custom field definition. Allows creating single-select or multi-select fields with predefined options that users can choose from.

Retrieve a specific select-type custom field by its unique identifier. Returns the complete field configuration including its available options.

Update an existing select-type custom field definition. Allows modifying the name or API name of an existing select or multi-select field.

Create a new option for a select-type custom field. Adds a new choice to the dropdown menu of an existing single-select or multi-select field.

Retrieve all available options for select-type custom fields. Options are the individual choices that appear in dropdown menus for single-select and multi-select custom fields. Filter by custom field to see options for a specific field.

Retrieve a specific custom field option by its unique identifier. Returns the option's value and the custom field it belongs to.

Update an existing custom field option. Allows modifying the display value of a dropdown choice.

Retrieve all divisions configured in the organization. Divisions represent the highest level of organizational hierarchy, grouping multiple departments together. Examples include business units like Sales Division, Engineering Division, or regional divisions like North America and Europe. Requires Admin scope.

Retrieve detailed information about a specific division by its unique identifier. Returns the division name and related organizational data.

Add a new department to the organizational structure. Departments are used to categorize jobs and appear as filters on the career site. Requires write permissions.

Retrieve a paginated list of all departments in the organization. Departments are used to categorize jobs and organize the hiring process by team or business unit. Useful for building career site filters and syncing organizational structure.

Retrieve complete information about a specific department using its unique identifier. Returns the department name, associated jobs, and organizational relationships.

Modify an existing department's information, such as renaming it. Useful for organizational restructuring or keeping department names in sync with external HR systems. Requires write permissions.

Permanently remove a department from the organizational structure. Before deleting, ensure no jobs are assigned to this department or reassign them first. Requires write permissions.

Retrieve all forms configured in the organization. Forms are customizable questionnaires used to collect structured information from candidates during the application process. They can include text fields, multiple choice questions, file uploads, and more. Requires Admin scope.

Retrieve detailed information about a specific form by its unique identifier. Returns the form configuration, title, and structure.

Retrieve all questions used across forms. Questions define what information is collected from candidates, including the question text, type such as text, select, or file upload, and whether an answer is required. Filter by form to see questions for a specific form.

Retrieve a specific form question by its unique identifier. Returns the complete question configuration including text, type, and validation rules.

Retrieve candidate responses to form questions. Answers contain the actual data submitted by candidates when completing application forms or questionnaires.

Retrieve a specific form answer by its unique identifier. Returns the complete response including the question asked and the candidate's answer.

Retrieve all scheduled interviews across the organization. Interviews are meetings arranged between candidates and team members during the hiring process. This endpoint is read-only as interviews are created through the Teamtailor UI or calendar integrations. Requires Admin scope.

Retrieve detailed information about a specific interview by its unique identifier. Returns the complete interview record including scheduling details, participants, and location. This endpoint is read-only.

Create a new job posting in the recruitment system. The job can be created as a draft for review or published immediately to your career site. You must specify a user who will own and manage the job. Requires write permissions.

Retrieve a paginated list of all job postings in the system. Jobs represent open positions that candidates can apply for. You can filter by status, department, location, and other criteria. The jobs visible depend on your API key scope where Public keys see only published jobs while Admin keys see all jobs including drafts and archived positions.

Retrieve complete information about a specific job posting using its unique identifier. Returns the full job details including title, description, requirements, application form settings, and all associated data. Useful for displaying job details on external career sites or integrating with job boards.

Modify an existing job posting. Use this to update job details, change the status, or edit the description. Commonly used to publish draft jobs, archive filled positions, or update job requirements. Requires write permissions.

Permanently remove a job posting and all its associated data from the system. This action cannot be undone. Consider archiving the job instead if you want to preserve historical data and candidate records. Requires write permissions.

Submit a new job application connecting a candidate to a specific job position. This creates the link between a candidate and a job and places them into the hiring pipeline. Requires Admin scope with write permissions.

Retrieve a paginated list of all job applications in the system. Job applications represent candidates who have applied for specific positions and track their progress through the hiring pipeline. You can filter by stage type, specific candidate, specific job, and date ranges. Requires Admin scope.

Retrieve complete information about a specific job application using its unique identifier. Returns the full application details including the candidate's current stage, application history, match score, and any rejection information. Requires Admin scope.

Modify a job application to update the cover letter. Requires Admin scope with write permissions.

Retrieve all employment offers that have been extended to candidates. Job offers track the formal offer process including salary details, start dates, and candidate responses. This endpoint is read-only as offers are created through the Teamtailor UI. Requires Admin scope.

Retrieve detailed information about a specific job offer by its unique identifier. Returns the complete offer record including status, terms, and candidate response. This endpoint is read-only.

Add a new office location to the organization. Locations are used to categorize jobs geographically and appear as filters on the career site. Requires write permissions.

Retrieve a paginated list of all office locations in the organization. Locations represent physical offices or work sites where jobs are available. They appear as filters on the career site allowing candidates to find positions near them.

Retrieve complete information about a specific location using its unique identifier. Returns the full address details, geographic coordinates if available, and associated region information.

Modify an existing location's information such as its name or address details. Useful when office addresses change or names need updating. Requires write permissions.

Permanently remove a location from the organization. Before deleting, ensure no jobs are assigned to this location or reassign them first. Requires write permissions.

Add a new note or comment to a candidate's profile. Use this to record interview feedback, document observations, or share information with the hiring team about a candidate. Requires Admin scope with write permissions.

Retrieve a paginated list of all notes and comments recorded on candidates and their job applications. Notes capture recruiter observations, interview feedback, and important information gathered during the hiring process. Requires Admin scope.

Retrieve the complete content of a specific note using its unique identifier. Returns the full note text, information about who wrote it, when it was created, and which candidate or application it relates to. Requires Admin scope.

Modify the content of an existing note. Use this to correct information, add additional details, or update feedback after further consideration. Requires Admin scope with write permissions.

Permanently remove a note from a candidate or job application. Use this to delete outdated information, remove inappropriate comments, or clean up test data. This action cannot be undone. Requires Admin scope with write permissions.

Retrieve all onboarding records for hired candidates. Onboardings track the new hire process from offer acceptance through their first day and beyond, including paperwork completion, equipment setup, and orientation scheduling. Filter by candidate to see their onboarding status. Requires Admin scope.

Retrieve detailed information about a specific onboarding record by its unique identifier. Returns the complete onboarding status and new hire information.

Add a new rejection reason option.

Retrieve all configured rejection reasons available in the system. Rejection reasons provide standardized explanations for why candidates were not selected or why they withdrew from the process. These reasons are used for analytics and consistent candidate communication.

Retrieve a specific rejection reason by ID.

Modify an existing rejection reason. Requires reject reason id from list_reject_reasons.

Remove a rejection reason option. Requires reject reason id from list_reject_reasons.

Submit a new job requisition for approval. This initiates the hiring approval workflow, requesting permission to fill a position. Requires location_id from list_locations. Optionally use list_departments for department_id. Note - Requires Requisitions feature to be enabled on the Teamtailor account.

Retrieve all job requisitions and their approval status. Requisitions are formal requests to fill a position, often requiring approval from managers or HR before a job posting can be created. They support headcount planning and budget control for hiring. Requires Admin scope.

Retrieve detailed information about a specific requisition by its unique identifier. Returns the complete requisition including approval status, headcount, and organizational assignment.

Modify an existing requisition's details such as title, headcount, or reason. Requires requisition id from list_requisitions. Note that approval status changes may be handled through separate workflow actions. Note - Requires Requisitions feature to be enabled on the Teamtailor account.

Create a new job role category in the organization. Roles classify jobs by function or area of expertise such as Engineering, Sales, or Marketing.

Retrieve all job role categories configured in the organization. Roles classify jobs by function or area of expertise such as Engineering, Sales, Marketing, or Customer Support. They appear on career sites as filters helping candidates find relevant positions. Requires Admin scope.

Retrieve a specific role by its unique identifier. Returns the role name and configuration.

Delete a job role category from the organization. Requires role id from list_roles.

Add a new stage to a job's hiring pipeline. Use this to customize the recruitment workflow with additional steps like technical assessments, panel interviews, or reference checks. Requires write permissions.

Retrieve all hiring pipeline stages across jobs. Stages represent the steps candidates progress through during recruitment, such as Application Received, Phone Screen, Interview, Offer, and Hired. Filter by job to see the pipeline for a specific position.

Retrieve complete information about a specific hiring stage using its unique identifier. Returns the stage name, type, position in the pipeline, and which job it belongs to.

Retrieve all available stage type definitions that categorize stages in the hiring pipeline. Stage types include Inbox for new applications, In Process for active candidates being evaluated, and Hired for successful candidates.

Retrieve a specific stage type by its unique identifier. Returns the stage type name and configuration.

Add a new team for organizing users and managing access. Requires user_id from list_users as the team manager.

Retrieve all teams configured in the organization. Teams group users together for permission management and collaborative hiring. Team membership determines which candidates and jobs users can access. Requires Admin scope.

Retrieve detailed information about a specific team by ID.

Update an existing team's information. Requires team id from list_teams.

Remove a team from the organization. Requires team id from list_teams.

Add a user to a team. Requires user_id from list_users and team_id from list_teams.

Retrieve team membership records showing user-team associations.

Retrieve details of a specific team membership by ID.

Remove a user from a team. Requires membership id from list_team_memberships.

Add a new team member to the Teamtailor system. Use this to onboard new recruiters, create hiring manager accounts, or set up automated user provisioning from your HR system. Requires Admin scope with write permissions.

Retrieve a paginated list of all users in the system. Users include recruiters, hiring managers, administrators, and other team members involved in the hiring process. Each user has a role determining their permissions and capabilities. Requires Admin scope.

Retrieve complete information about a specific user using their unique identifier. Returns the user's profile details, role, visibility settings, and relationships to teams and activities. Requires Admin scope.

Modify an existing user's profile information, role, or visibility settings. Use this to update names, change permission levels, or control visibility on the career site. Requires Admin scope with write permissions.

Remove a user account from the system. Before deleting, reassign any jobs owned by this user to another team member. This action cannot be undone. Requires Admin scope with write permissions.