hires_list_interviews
List interviews with optional filters by job, application, candidate, interviewer, date, or timestamps for incremental sync. Returns paginated results. Always pass include=candidate when surfacing results in the agenda widget — without it, the widget can only show candidate IDs and cannot link ca...
This record as markdown: /tools/com-100hires-100hires/hires-list-interviews.md
What hires_list_interviews does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_interviews to retrieve information from 100Hires - AI ATS & Recruitment Software without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | Filter by interview date (YYYY-MM-DD, UTC) |
page | number | — | Page number (default 1) |
size | number | — | Page size (default 20) |
job_id | number | — | Filter interviews by job ID |
include | string | — | Comma-separated related resources to embed: candidate, application, job. Set to `candidate` (or include `candidate` in the list) so the widget can link intervie |
company_id | number | — | Filter by company ID. Omit for all accessible companies. |
candidate_id | number | — | Filter interviews by candidate ID |
created_after | number | string | — | Return only interviews created at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but t |
updated_after | number | string | — | Return only interviews updated at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but t |
application_id | number | — | Filter interviews by application ID |
interviewer_user_id | number | — | Filter interviews by interviewer user ID |
Parameters from the server's own tool schema.
Why hires_list_interviews is rated Low
This tool queries and retrieves interview records with optional filtering and pagination. It has no side effects: it does not create, modify, delete, or execute operations. The notes about include parameters and budget management are implementation details for data retrieval optimization, not indicators of write/execute/destructive capability.
From the tool's definition Tool name is "hires_list_interviews" and description states "List interviews with optional filters" and "Returns paginated results" — classic read operations that retrieve data without modification.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs hires_list_interviews safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires - AI ATS & Recruitment Software, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_list_interviews, this is the rule to start with:
hires_list_interviews is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires - AI ATS & Recruitment Software, apply this rule, and every hires_list_interviews call is checked against it from then on.
Questions about hires_list_interviews
List interviews with optional filters by job, application, candidate, interviewer, date, or timestamps for incremental sync. Returns paginated results. Always pass include=candidate when surfacing results in the agenda widget — without it, the widget can only show candidate IDs and cannot link cards to candidate profiles. Avoid include=job on large pages (embeds full job description per interview); if the response exceeds the budget the tool returns isError:true with error_code=response_too_large and retry hints. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.
hires_list_interviews accepts 11 parameters: date, page, size, job_id, include, company_id, candidate_id, created_after, updated_after, application_id, interviewer_user_id. The full parameter table on this page comes from the server's own tool schema.
Register the 100Hires - AI ATS & Recruitment Software MCP server in PolicyLayer and add a rule for hires_list_interviews: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 100Hires - AI ATS & Recruitment Software. Nothing to install.
hires_list_interviews is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hires_list_interviews rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for hires_list_interviews. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
hires_list_interviews is provided by the 100Hires - AI ATS & Recruitment Software MCP server (https://mcp.100hires.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires - AI ATS & Recruitment Software, and thousands of servers like it.
Across the catalogue