Lever ACTION
List Opportunity Items
Returns sub-records attached to a single opportunity (candidate): notes, feedback, interviews, resumes, files, or offers. Use this when asked about a candidate's notes, interview feedback/scorecards, scheduled interviews, resumes, attached files, or offer. Set
resource to choose which: notes (recruiter notes), feedback (interview scorecards — each with panel id, interviewer, and score), interviews (scheduled interviews — each with panel id, date, interviewers), resumes (parsed resumes — each with a resume id), files (other attached documents — each with file id, name, extension), or offers (offer details). Use Search Opportunities to find the opportunity ID first. The panel IDs returned by interviews/feedback are used by Submit Feedback; the resumes resource returns each resume's parsed data inline (status, file info, and extracted fields). For notes, feedback, interviews, and offers this returns one page (up to limit); if the response's hasNext is true, pass its next value to offset to fetch the following page. Gotcha: resumes and files are not paginated — Lever returns the full set in a single payload with no hasNext/next cursor, and limit/offset are ignored, so do not expect cursor metadata for them. Example: to read a candidate's interview feedback, call with opportunityId="<id>", resource="feedback" → returns feedback records each with panel id, interviewer, score, and completed form fields. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Lever account once, then configure and run List Opportunity Items from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "lever-list-opportunity-items",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
lever: { authProvisionId: "apn_xxxxxxx" },
opportunityId: "Opportunity ID",
resource: "Resource",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "lever-list-opportunity-items",
"configured_props": {
"lever": { "authProvisionId": "apn_xxxxxxx" },
"opportunityId": "Opportunity ID",
"resource": "Resource"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "lever",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "lever-list-opportunity-items",
arguments: {
opportunityId: "Opportunity ID",
resource: "Resource",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
opportunityId Opportunity ID | string | The ID of the opportunity whose items to retrieve. Use Search Opportunities to find opportunity IDs. Required |
resource Resource | string | Which sub-records to return for the opportunity. Required |
limit Limit | integer | Maximum number of items to return (1–100). Defaults to 100. Ignored for resumes/files, which Lever does not paginate. Optional |
offset Offset (cursor) | string | Pagination cursor. Pass the next value from a previous response to fetch the next page. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- lever-list-opportunity-items
- Version
- 0.0.2
- App
- Lever
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗