Kula MCP: Sample Prompts and Best Practices
Last updated: June 1, 2026
This guide provides sample prompts and best practices for using Kula MCP with Claude. The examples in this article have been validated against the Kula API and demonstrate common recruiting workflows, including candidate management, pipeline updates, interview scheduling, reporting, and webhook management.
Understanding How Kula MCP Works
Most Kula MCP actions require an ID, such as a job ID, candidate ID, application ID, or stage ID.
The standard workflow is:
Search or list records to retrieve the required ID.
Use the returned ID to perform an action.
For example:
Find Job → Get job_id → Perform action
Find Candidate → Get candidate_id → Perform action
Claude automatically performs these chained actions when you describe your intent in natural language.
Candidate Lookup and Research
Find candidates by name and job
Prompt
Find all candidates named Priya who applied to the Backend Engineer job.
Workflow
Search the job.
Retrieve the job ID.
Search candidates matching the name within that job.
View active applications for a job
Prompt
Show me all active applications for the Senior Developer role.
Workflow
Search for the job.
Retrieve the job ID.
List active applications.
View complete candidate details
Prompt
Get full profile for candidate ID 1290875.
Returns
Candidate profile
Applications
Tags
Skills
Resume information
Location details
Find candidates by skills
Prompt
Find candidates with Python and React skills.
Workflow
Search for Python skill.
Search for React skill.
Search candidates using the matching skill IDs.
Pipeline Management
Move a candidate to a different stage
Prompt
Move candidate Rohan Sharma's application for the Software Engineer role to the Technical Interview stage.
Workflow
Find the candidate.
Retrieve the application.
Retrieve job stages.
Update the application stage.
Find stale applications
Prompt
Show me all applications stuck in Screening for more than 7 days.
Workflow
Retrieve stages for the job.
Find the Screening stage ID.
List applications that have not moved recently.
View applications by status
Prompt
List all rejected applications for job ID 47992.
Workflow
Retrieve applications.
Filter by rejected status.
Interview Scheduling
Interview scheduling typically involves multiple dependent actions.
Recommended scheduling workflow
Always follow this sequence:
Validate organizers.
Check interviewer availability.
Create the interview.
Skipping organizer validation is a common cause of scheduling failures.
Schedule a Google Meet interview
Prompt
Schedule a 1-hour Google Meet interview for application 3951003 with Deeshath as interviewer, tomorrow at 10 AM IST.
Requirements
Start time must be on a 15-minute boundary.
Use a valid timezone.
Example:
2026-06-03T10:00:00+05:30
Timezone:
Asia/Kolkata
Schedule a Zoom interview
Prompt
Schedule a 45-minute Zoom call for application 6394193 with user 2196 as both host and interviewer.
Requirements
Zoom interviews require a host ID.
The host must also be included in the interviewer list.
Use conference host lookup before scheduling.
Schedule using an interview plan
Recommended approach
Prompt
Schedule the Technical Round interview for application 3951003 following the interview plan.
Benefits
When an interview plan exists, scheduling through the plan automatically inherits:
Scorecard templates
Email templates
Interview duration
Interview configuration
This reduces manual setup and errors.
View upcoming interviews
Prompt
Show me all interviews scheduled for this week via Zoom.
Audit canceled interviews
Prompt
Show me all canceled interviews from the past 30 days.
Adding Candidates
Add a candidate to a pipeline
Prompt
Add John Doe (john@example.com) to the Senior Engineer pipeline at the Applied stage.
Workflow
Find the job.
Retrieve available stages.
Create the candidate.
Place the candidate in the selected stage.
Add a candidate using LinkedIn
Prompt
Add candidate from LinkedIn: https://linkedin.com/in/janedoe, first name Jane, last name Doe.
Requirements
At least one of the following must be provided:
Email address
LinkedIn profile URL
Add a candidate with skills and tags
Prompt
Add Raj Kumar (raj@email.com) with skills Python and SQL and tag Engineering to the Data Analyst role.
Webhook Management
Debug a webhook
Prompt
Check the recent delivery logs for webhook ID abc123.
Workflow
Retrieve webhook details.
Retrieve webhook logs.
Review delivery status and response codes.
Update webhook subscriptions
Prompt
Update webhook abc123 to also subscribe to interview.cancelled events.
View all webhooks
Prompt
Show me all configured webhooks and their subscribed events.
Returns:
Webhook name
Endpoint URL
Status
Subscribed events
Interview Audit and Reporting
Count interviews for a job
Prompt
How many interviews are scheduled for job ID 26120 this month?
Review interviewer workload
Prompt
Show me all interviews where Deeshath is the interviewer this week.
Track AI Note Taker usage
Prompt
Which interviews have AI Note Taker enabled?
Best Practices
Always resolve IDs before taking action
Never assume an ID.
Use names or search terms and allow Claude to retrieve the correct ID before performing updates.
This helps prevent changes to the wrong record.
Use candidate search instead of candidate listing
Use candidate search when investigating recruiting issues because it supports:
Name searches
Email searches
Resume content searches
Important limitation
The minimum supported search limit is:
20
Using a limit below 20 returns an error.
Recommended:
Omit the limit parameter, or
Use values between 20 and 50
Resolve stage IDs for each job
Stage names are configured per job.
Always retrieve stages for the specific job before moving candidates between stages.
Use pagination for large datasets
When retrieving large volumes of data:
Use larger page sizes.
Follow cursor-based pagination when provided.
Reset the cursor whenever filters change.
Use IST correctly for Indian teams
Recommended timezone:
Asia/Kolkata
Example timestamp:
2026-06-03T10:00:00+05:30
Follow the webhook debugging workflow
When troubleshooting webhook failures:
Verify the webhook exists.
Confirm the endpoint URL.
Review delivery logs.
Send a test event.
Prefer plan-driven interview scheduling
When interview plans are configured, use them instead of manual scheduling.
Benefits include:
Consistent interview setup
Automatic scorecards
Standardized email templates
Reduced scheduling errors
ID Reference Guide
Required ID | Retrieve Using |
|---|---|
Job ID | Search jobs |
Application ID | List applications |
Candidate ID | Search candidates |
Stage ID | List job stages |
Organizer ID | List valid organizers |
Stage Activity ID | Retrieve interview plan |
Scorecard Template ID | List scorecard templates |
User ID | List users |
Known Limitations
Candidate search limits
The minimum supported limit is 20.
Values below 20 return validation errors.
Interview start times
Start times must:
Be in the future.
Use a 15-minute interval.
Have zero seconds.
Examples:
10:00
10:15
10:30
10:45
Interview duration
Interview duration must:
Be between 15 and 1440 minutes.
Be a multiple of 15 minutes.
One-on-one interviews
One-on-one interviews require exactly one interviewer.
Use panel interviews for two or more interviewers.
Zoom interviews
Zoom interviews require:
A valid host ID.
The host to also be listed as an interviewer.
Onsite interviews
Onsite interviews require a valid office ID.
Retrieve available offices before scheduling.
Candidate creation requirements
Creating a candidate requires:
First name, and
Either an email address or a LinkedIn profile URL.