Lever Ops Control Plane

by app.vercel.ats-ops-control-plane-gateway

Server Details

Ask Lever the messy recruiting-ops questions dashboards miss by connecting opportunities, applications, stages, notes, feedback, interviews, referrals, postings, requisitions, offers, users, sources, tags, files, resumes, and archive reasons. Find referral SLA misses, stale opportunities by owner, feedback debt by interviewer and hiring team, funnel leakage by recruiter/source/team, requisition fill-risk, offer hygiene gaps, archive-reason drift, and bottleneck owners. No dashboard build. No SQL

Status: Healthy
Last Tested: 2026-06-06 01:35
Transport: Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client

Glama

MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

108 tools

add_opportunity_linksInspect

Call Lever POST /opportunities/:opportunity/addLinks for opportunity contact/source/tag maintenance.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

add_opportunity_sourcesInspect

Call Lever POST /opportunities/:opportunity/addSources for opportunity contact/source/tag maintenance.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

add_opportunity_tagsInspect

Call Lever POST /opportunities/:opportunity/addTags for opportunity contact/source/tag maintenance.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

add_requisition_field_optionsInspect

Use Lever POST /requisition_fields/:id/options for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

apply_to_postingInspect

Apply to a Lever posting via POST /postings/:posting/apply. This is the documented create-application path.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`posting_id`	Yes	Lever posting ID.

create_feedback_templateInspect

Use Lever POST /feedback_templates for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`template_id`	No	Unused for create operations.

create_form_templateInspect

Use Lever POST /form_templates for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`template_id`	No	Unused for create operations.

create_opportunityInspect

Create a Lever opportunity via POST /opportunities.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.

create_opportunity_feedbackInspect

Use Lever POST /opportunities/:opportunity/feedback for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	No	Unused for create operations.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

create_opportunity_formInspect

Create a Lever profile form via POST /opportunities/:opportunity/forms.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

create_opportunity_interviewInspect

Use Lever POST /opportunities/:opportunity/interviews for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	No	Unused for create operations.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

create_opportunity_noteInspect

Create a Lever note via POST /opportunities/:opportunity/notes.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

create_opportunity_panelInspect

Use Lever POST /opportunities/:opportunity/panels for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	No	Unused for create operations.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

create_postingInspect

Create a Lever posting via POST /postings.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

create_requisitionInspect

Use Lever POST /requisitions for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	No	Unused for create operations.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

create_requisition_fieldInspect

Use Lever POST /requisition_fields for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	No	Unused for create operations.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

create_userInspect

Use Lever POST /users for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`user_id`	No	Unused for create operations.
`actor_id`	Yes	Lever user ID associated with this action when needed.

create_webhookInspect

Create a Lever API webhook via POST /webhooks.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.

deactivate_userInspect

Use Lever POST /users/:id/deactivate for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`user_id`	Yes	Lever user ID.
`actor_id`	Yes	Lever user ID associated with this action when needed.

delete_feedback_templateInspect

Use Lever DELETE /feedback_templates/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`template_id`	Yes	Lever template ID.

delete_form_templateInspect

Use Lever DELETE /form_templates/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`template_id`	Yes	Lever template ID.

delete_opportunity_feedbackInspect

Use Lever DELETE /opportunities/:opportunity/feedback/:record for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever record ID for this collection.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

delete_opportunity_fileInspect

Delete a Lever opportunity file via DELETE /opportunities/:opportunity/files/:file.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`file_id`	Yes	Lever file ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

delete_opportunity_interviewInspect

Use Lever DELETE /opportunities/:opportunity/interviews/:record for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever record ID for this collection.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

delete_opportunity_noteInspect

Delete a Lever note via DELETE /opportunities/:opportunity/notes/:noteId.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`note_id`	Yes	Lever note ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

delete_opportunity_panelInspect

Use Lever DELETE /opportunities/:opportunity/panels/:record for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever record ID for this collection.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

delete_requisitionInspect

Use Lever DELETE /requisitions/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

delete_requisition_fieldInspect

Use Lever DELETE /requisition_fields/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

delete_requisition_field_optionsInspect

Use Lever DELETE /requisition_fields/:id/options for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

delete_webhookInspect

Delete one Lever API-created webhook via DELETE /webhooks/:webhookId.

ParametersJSON Schema

Name	Required	Description	Default
`body`	No	Optional JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`webhook_id`	Yes	Lever webhook ID.

download_opportunity_fileInspect

Download one Lever opportunity file as base64 via GET /opportunities/:opportunity/files/:file/download.

ParametersJSON Schema

Name	Required	Description
`reason`	Yes	Reason for returning a base64 file payload.
`file_id`	Yes	Lever file ID.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`max_bytes`	No
`opportunity_id`	Yes	Lever opportunity ID.
`acknowledge_sensitive_data`	No	Must be true for high-sensitivity reads such as EEO PII, diversity surveys, or download URLs.

download_opportunity_offer_fileInspect

Download a sent or signed Lever offer file as base64 via GET /opportunities/:opportunity/offers/:offer/download.

ParametersJSON Schema

Name	Required	Description
`reason`	Yes	Reason for returning a base64 file payload.
`status`	Yes	Offer document status to download.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`offer_id`	Yes	Lever offer ID.
`max_bytes`	No
`opportunity_id`	Yes	Lever opportunity ID.
`acknowledge_sensitive_data`	No	Must be true for high-sensitivity reads such as EEO PII, diversity surveys, or download URLs.

download_opportunity_resumeInspect

Download one Lever resume file as base64 via GET /opportunities/:opportunity/resumes/:resume/download.

ParametersJSON Schema

Name	Required	Description
`reason`	Yes	Reason for returning a base64 file payload.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`max_bytes`	No
`resume_id`	Yes	Lever resume ID.
`opportunity_id`	Yes	Lever opportunity ID.
`acknowledge_sensitive_data`	No	Must be true for high-sensitivity reads such as EEO PII, diversity surveys, or download URLs.

get_archive_reasonInspect

Retrieve one Lever archive reason.

ParametersJSON Schema

Name	Required	Description	Default
`archive_reason_id`	Yes	Lever archive reason ID.

get_contactInspect

Retrieve one Lever contact. Default output omits name, headline, emails, and phones; full contact details require detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`contact_id`	Yes	Lever contact ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational

get_control_plane_capabilitiesInspect

Show which Lever control-plane tool families and API permissions are available.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

get_diversity_surveyInspect

Retrieve the Lever diversity survey configuration for a posting. Requires a compliance reason and acknowledge_sensitive_data=true.

ParametersJSON Schema

Name	Required	Description
`reason`	Yes	Compliance reason for reading diversity survey configuration.
`posting_id`	Yes	Lever posting ID.
`acknowledge_sensitive_data`	No	Must be true for high-sensitivity reads such as EEO PII, diversity surveys, or download URLs.

get_feedback_templateInspect

Retrieve one Lever feedback template. Full template instructions and fields require detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`feedback_template_id`	Yes	Lever feedback template ID.

get_form_templateInspect

Retrieve one Lever profile form template. Full instructions and fields require detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`form_template_id`	Yes	Lever form template ID.

get_opportunityInspect

Retrieve one Lever opportunity. Default output omits contact PII; use detail_profile=contact with a reason when names, emails, phones, links, and URLs are needed.

ParametersJSON Schema

Name	Required	Description	Default
`expand`	No	Lever expand parameter for endpoint-supported objects.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`include`	No	Lever include parameter for endpoint-supported fields.
`detail_profile`	No	operational omits contact PII; contact includes name, emails, phones, links, and URLs.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_applicationInspect

Retrieve one application attached to a Lever opportunity. Deprecated by Lever in favor of get_opportunity with expand=applications, but maintained for backwards compatibility.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`application_id`	Yes	Lever application ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_feedbackInspect

Retrieve one Lever feedback form. Default output keeps scores, timestamps, users, and field presence without returning field values.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`feedback_id`	Yes	Lever feedback ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_fileInspect

Retrieve file metadata for one Lever opportunity file. Default output omits the download URL; full metadata requires detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`file_id`	Yes	Lever file ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_formInspect

Retrieve one Lever profile form attached to an opportunity. Default output summarizes fields without values; full field values require a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`form_id`	Yes	Lever profile form ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_interviewInspect

Retrieve one Lever interview by ID.

ParametersJSON Schema

Name	Required	Description	Default
`interview_id`	Yes	Lever interview ID.
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_noteInspect

Retrieve one Lever opportunity note. Default output shows note metadata; full note values require detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`note_id`	Yes	Lever note ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_offerInspect

Retrieve one Lever offer by scanning the documented Lever offers list for this opportunity. Default output supports offer hygiene checks without returning offer field values, signature data, or download URLs.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`offer_id`	Yes	Lever offer ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_panelInspect

Retrieve one Lever interview panel attached to an opportunity.

ParametersJSON Schema

Name	Required	Description	Default
`panel_id`	Yes	Lever panel ID.
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_referralInspect

Retrieve one Lever referral form for an opportunity.

ParametersJSON Schema

Name	Required	Description	Default
`referral_id`	Yes	Lever referral ID.
`opportunity_id`	Yes	Lever opportunity ID.

get_opportunity_resumeInspect

Retrieve resume metadata for one Lever opportunity resume. Default output omits parsed resume details and download URLs; full metadata requires a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`resume_id`	Yes	Lever resume ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

get_postingInspect

Retrieve one Lever posting. Default output omits content and salary fields; use detail_profile=full with a reason when needed.

ParametersJSON Schema

Name	Required	Description	Default
`expand`	No	Lever expand parameter for endpoint-supported objects.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`include`	No	Lever include parameter for endpoint-supported fields.
`posting_id`	Yes	Lever posting ID.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational

get_posting_application_questionsInspect

Retrieve Lever posting application questions and posting apply-form schema.

ParametersJSON Schema

Name	Required	Description	Default
`posting_id`	Yes	Lever posting ID.

get_requisitionInspect

Retrieve one Lever requisition. Default output omits compensation band, internal notes, custom fields, and approval internals; full details require a reason.

ParametersJSON Schema

Name	Required	Description	Default
`expand`	No	Lever expand parameter for endpoint-supported objects.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`include`	No	Lever include parameter for endpoint-supported fields.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`requisition_id`	Yes	Lever requisition ID.

get_requisition_fieldInspect

Retrieve one Lever requisition field schema.

ParametersJSON Schema

Name	Required	Description	Default
`requisition_field_id`	Yes	Lever requisition field identifier.

get_stageInspect

Retrieve one Lever stage.

ParametersJSON Schema

Name	Required	Description	Default
`stage_id`	Yes	Lever stage ID.

get_userInspect

Retrieve one Lever user.

ParametersJSON Schema

Name	Required	Description	Default
`user_id`	Yes	Lever user ID.

list_archive_reasonsInspect

List Lever archive reasons, optionally filtered by hired or non-hired type.

ParametersJSON Schema

Name	Required	Description	Default
`type`	No

list_audit_eventsInspect

List Lever audit events for security and access investigations. This endpoint is a Lever add-on. Default output summarizes meta keys; full meta requires a reason.

ParametersJSON Schema

Name	Required	Description	Default
`type`	No	Filter returned events to a single event type.
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`user_id`	No	Filter by acting user ID, or literal null for no-user events.
`target_id`	No	Filter by target resource ID. Requires target_type in Lever.
`target_type`	No	Filter by target resource type.
`created_at_end`	No
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`created_at_start`	No	Unix timestamp in milliseconds.

list_deleted_applicationsInspect

List deleted Lever applications within a required 30-day deleted_at window.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`deleted_at_end`	Yes	Exclusive upper bound in Unix milliseconds. Window may not exceed 30 days.
`deleted_at_start`	Yes	Inclusive lower bound in Unix milliseconds.

list_deleted_opportunitiesInspect

List deleted Lever opportunities within a required 30-day deleted_at window.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`deleted_at_end`	Yes	Exclusive upper bound in Unix milliseconds. Window may not exceed 30 days.
`deleted_at_start`	Yes	Inclusive lower bound in Unix milliseconds.

list_deleted_postingsInspect

List deleted Lever postings within a required 30-day deleted_at window.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`deleted_at_end`	Yes	Exclusive upper bound in Unix milliseconds. Window may not exceed 30 days.
`deleted_at_start`	Yes	Inclusive lower bound in Unix milliseconds.

list_disposition_stagesInspect

List Lever disposition stages used for archive/disposition reporting.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

list_eeo_responsesInspect

List anonymous Lever EEO responses for compliance analysis. Use carefully and only with an appropriate compliance reason.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`expand`	No	Comma-separated fields Lever allows expanding, such as contact, hiringManager, posting.
`reason`	Yes	Compliance reason for reading anonymous EEO responses.
`created_at_end`	No
`created_at_start`	No	Unix timestamp in milliseconds.

list_eeo_responses_with_piiInspect

List Lever EEO responses with PII. This is high-sensitivity compliance data and requires both a reason and acknowledge_sensitive_data=true.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`expand`	No	Comma-separated fields Lever allows expanding, such as contact, hiringManager, posting.
`reason`	Yes	Compliance reason for reading EEO responses with PII.
`created_at_end`	No
`created_at_start`	No	Unix timestamp in milliseconds.
`acknowledge_sensitive_data`	No	Must be true for high-sensitivity reads such as EEO PII, diversity surveys, or download URLs.

list_feedback_templatesInspect

List active Lever feedback templates, useful for interview-loop and scorecard-design audits.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational

list_form_templatesInspect

List Lever profile form templates, useful for profile-form hygiene and structured-data coverage audits.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`include`	No	Comma-separated attributes to include, such as text, group, fields.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational

list_opportunitiesInspect

List Lever opportunities for recruiting-ops investigations. Default output omits contact PII while preserving stage, owner, source, tag, application, archive, snooze, and timestamp fields.

ParametersJSON Schema

Name	Required	Description	Default
`tag`	No	Comma-separated tag filters. Tags are case-sensitive.
`email`	No	Filter by exact candidate contact email.
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`expand`	No	Lever expand parameter for endpoint-supported objects.
`origin`	No	Comma-separated origin filters, such as sourced or applied.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`source`	No	Comma-separated source filters.
`include`	No	Lever include parameter for endpoint-supported fields.
`snoozed`	No
`archived`	No
`stage_id`	No	Comma-separated stage IDs.
`contact_id`	No	Comma-separated contact IDs.
`posting_id`	No	Comma-separated posting IDs.
`created_at_end`	No
`detail_profile`	No	operational omits contact PII; contact includes name, emails, phones, links, and URLs.	operational
`updated_at_end`	No
`advanced_at_end`	No
`archived_at_end`	No
`confidentiality`	No
`created_at_start`	No	Unix timestamp in milliseconds.
`updated_at_start`	No
`advanced_at_start`	No
`archive_reason_id`	No	Comma-separated archive reason IDs.
`archived_at_start`	No
`archived_posting_id`	No	Comma-separated archived posting IDs.

list_opportunity_applicationsInspect

List applications attached to one Lever opportunity. Deprecated by Lever in favor of get_opportunity with expand=applications, but maintained for backwards compatibility.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_feedbackInspect

List feedback forms for a Lever opportunity. Default output keeps scores, timestamps, users, and field presence without returning field values.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_file_actionsInspect

List file-related activity for a Lever opportunity, useful for resume/import/change hygiene without downloading files.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`opportunity_id`	Yes	Lever opportunity ID.
`occurred_at_end`	No
`occurred_at_start`	No	Unix timestamp in milliseconds.

list_opportunity_filesInspect

List file metadata for a Lever opportunity. Default output omits download URLs; full metadata requires detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.
`uploaded_at_end`	No
`uploaded_at_start`	No	Unix timestamp in milliseconds.

list_opportunity_formsInspect

List additional forms attached to a Lever opportunity.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_interviewsInspect

List interviews for a Lever opportunity, including schedule metadata, panel/interviewer references, and feedback template references.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_notesInspect

List notes for a Lever opportunity. Default output shows note metadata and whether body text exists; full note values require detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_offersInspect

List offers for a Lever opportunity. Default output supports offer hygiene checks without returning offer field values, signature data, or download URLs.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_panelsInspect

List interview panels for a Lever opportunity.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_referralsInspect

List referrals for a Lever opportunity. This returns Lever's referral form payload; use it for referral-source and referral-SLA investigations.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`opportunity_id`	Yes	Lever opportunity ID.

list_opportunity_resumesInspect

List resume metadata for a Lever opportunity. Default output omits parsed resume details and download URLs; full metadata requires detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`opportunity_id`	Yes	Lever opportunity ID.

list_postingsInspect

List Lever postings for job, team, department, location, requisition, and distribution-channel analysis.

ParametersJSON Schema

Name	Required	Description	Default
`tag`	No	Comma-separated tag values.
`team`	No	Comma-separated team names.
`group`	No
`level`	No	Comma-separated deprecated level values.
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`state`	No
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`expand`	No	Lever expand parameter for endpoint-supported objects.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`include`	No	Lever include parameter for endpoint-supported fields.
`location`	No	Comma-separated location names.
`commitment`	No	Comma-separated work type names.
`department`	No	Comma-separated department names.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`updated_at_end`	No
`confidentiality`	No
`updated_at_start`	No	Unix timestamp in milliseconds.
`distributionChannel`	No	Comma-separated public/internal filters.

list_posting_usersInspect

List users and roles with access to one Lever posting, useful for confidential-posting access audits.

ParametersJSON Schema

Name	Required	Description	Default
`posting_id`	Yes	Lever posting ID.

list_requisition_fieldsInspect

List Lever requisition field schemas, optionally filtered by required flag or top-level type.

ParametersJSON Schema

Name	Required	Description	Default
`type`	No	Filter by top-level type, such as number, text, date, object, or dropdown.
`isRequired`	No	Filter requisition fields by required flag.

list_requisitionsInspect

List Lever requisitions for open headcount, filled headcount, owner, hiring manager, team, department, and status analysis.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`expand`	No	Lever expand parameter for endpoint-supported objects.
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`status`	No	Filter requisitions by Lever status, such as open.
`include`	No	Lever include parameter for endpoint-supported fields.
`created_at_end`	No
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational
`confidentiality`	No
`created_at_start`	No	Unix timestamp in milliseconds.
`requisition_code`	No

list_sourcesInspect

List Lever sources with counts, useful for source-quality analysis.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

list_stagesInspect

List all Lever pipeline stages.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

list_usersInspect

List Lever users for joining owners, hiring managers, recruiters, coordinators, interviewers, and approvers.

ParametersJSON Schema

Name	Required	Description
`email`	No	Filter by exact canonicalized email.
`limit`	No	Results per page. Lever accepts 1-100; default is endpoint-specific.
`cursor`	No	Lever pagination offset token from a previous response. Use next_cursor from the prior tool result.
`accessRole`	No	Comma-separated access roles or custom role IDs.
`includeDeactivated`	No
`external_directory_id`	No

list_webhooksInspect

List Lever API-created webhooks. Default output shows event and URL host only; full URLs/configuration require detail_profile=full with a reason.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Required when detail_profile requests contact, content, values, or full details.
`detail_profile`	No	operational returns an operations view; full returns the raw endpoint payload.	operational

reactivate_userInspect

Use Lever POST /users/:id/reactivate for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`user_id`	Yes	Lever user ID.
`actor_id`	Yes	Lever user ID associated with this action when needed.

remove_opportunity_linksInspect

Call Lever POST /opportunities/:opportunity/removeLinks for opportunity contact/source/tag maintenance.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

remove_opportunity_sourcesInspect

Call Lever POST /opportunities/:opportunity/removeSources for opportunity contact/source/tag maintenance.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

remove_opportunity_tagsInspect

Call Lever POST /opportunities/:opportunity/removeTags for opportunity contact/source/tag maintenance.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_contactInspect

Update one Lever contact via PUT /contacts/:contact.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`contact_id`	Yes	Lever contact ID.

update_feedback_templateInspect

Use Lever PUT /feedback_templates/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`template_id`	Yes	Lever template ID.

update_form_templateInspect

Use Lever PUT /form_templates/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`template_id`	Yes	Lever template ID.

update_opportunity_archived_stateInspect

Update a Lever opportunity archived state via PUT /opportunities/:opportunity/archived.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_opportunity_feedbackInspect

Use Lever PUT /opportunities/:opportunity/feedback/:record for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever record ID for this collection.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_opportunity_interviewInspect

Use Lever PUT /opportunities/:opportunity/interviews/:record for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever record ID for this collection.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_opportunity_noteInspect

Update a Lever note created via API using PUT /opportunities/:opportunity/notes/:note.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`note_id`	Yes	Lever note ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_opportunity_panelInspect

Use Lever PUT /opportunities/:opportunity/panels/:record for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever record ID for this collection.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_opportunity_stageInspect

Update a Lever opportunity stage via PUT /opportunities/:opportunity/stage.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`opportunity_id`	Yes	Lever opportunity ID.

update_postingInspect

Update a Lever posting via POST /postings/:posting.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`posting_id`	Yes	Lever posting ID.

update_requisitionInspect

Use Lever PUT /requisitions/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

update_requisition_fieldInspect

Use Lever PUT /requisition_fields/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

update_requisition_field_optionsInspect

Use Lever PUT /requisition_fields/:id/options for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`record_id`	Yes	Lever requisition or requisition-field ID.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.

update_userInspect

Use Lever PUT /users/:id for recruiting operations.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`user_id`	Yes	Lever user ID.
`actor_id`	Yes	Lever user ID associated with this action when needed.

update_webhooksInspect

Update one or more Lever API-created webhooks via PUT /webhooks/.

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON body to send to the documented Lever endpoint.
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.

upload_fileInspect

Upload a file through Lever's generic POST /uploads endpoint. Reads a local file path from the MCP host.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`actor_id`	Yes	Lever user ID associated with this action when needed.
`file_path`	Yes	Local file path on the machine running the MCP server.
`content_type`	No	Optional MIME type. Defaults to application/octet-stream.

upload_opportunity_fileInspect

Upload a file to a Lever opportunity via POST /opportunities/:opportunity/files. Reads a local file path from the MCP host.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Reason for this Lever write.	Requested through Lever Ops Control Plane.
`confirm`	No	Set false only when you explicitly want to block execution.
`dry_run`	No	When true, preview the write without sending it to Lever.
`file_path`	Yes	Local file path on the machine running the MCP server.
`perform_as`	Yes	Lever user ID for perform_as when the Lever endpoint needs one.
`content_type`	No	Optional MIME type. Defaults to application/octet-stream.
`opportunity_id`	Yes	Lever opportunity ID.

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [{ "email": "your-email@example.com" }]
}

The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Resources

Need Help?