Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

List interviews (agenda)

hires_list_interviews
Read-only

List interviews filtered by job, application, candidate, interviewer, date or timestamps. Pass include=candidate so the agenda widget can link cards to candidate profiles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, UTC
pageNo
sizeNo
job_idNo
includeNoEmbed: candidate, application, job
company_idNo
candidate_idNo
created_afterNoUnix seconds or ISO-8601
updated_afterNoUnix seconds or ISO-8601; for incremental sync
application_idNo
interviewer_user_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / application_id / description
      Removed value: -"Filter interviews by application ID"
    • removedInput schema / properties / candidate_id / description
      Removed value: -"Filter interviews by candidate ID"
    • removedInput schema / properties / company_id / description
      Removed value: -"Filter by company ID. Omit for all accessible companies."
    • changedInput schema / properties / created_after / description
      Previous value: -"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 truncated."New value: +"Unix seconds or ISO-8601"
    • changedInput schema / properties / date / description
      Previous value: -"Filter by interview date (YYYY-MM-DD, UTC)"New value: +"YYYY-MM-DD, UTC"
    • changedInput schema / properties / include / description
      Previous value: -"Comma-separated related resources to embed: candidate, application, job. Set to `candidate` (or include `candidate` in the list) so the widget can link interview cards to candidate profiles in the backoffice."New value: +"Embed: candidate, application, job"
    • removedInput schema / properties / interviewer_user_id / description
      Removed value: -"Filter interviews by interviewer user ID"
    • removedInput schema / properties / job_id / description
      Removed value: -"Filter interviews by job ID"
    • removedInput schema / properties / page / description
      Removed value: -"Page number (default 1)"
    • removedInput schema / properties / size / description
      Removed value: -"Page size (default 20)"
    • changedInput schema / properties / updated_after / description
      Previous value: -"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 truncated."New value: +"Unix seconds or ISO-8601; for incremental sync"
  2. Changed4 schema fields changed
    • changedInput schema / properties / created_after / description
      Previous value: -"Return only interviews created after this Unix timestamp (seconds)"New value: +"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 truncated."
    • changedInput schema / properties / created_after / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / updated_after / description
      Previous value: -"Return only interviews updated after this Unix timestamp (seconds)"New value: +"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 truncated."
    • changedInput schema / properties / updated_after / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / include / description
      Previous value: -"Comma-separated related resources to embed: candidate, application, job"New value: +"Comma-separated related resources to embed: candidate, application, job. Set to `candidate` (or include `candidate` in the list) so the widget can link interview cards to candidate profiles in the backoffice."
  4. Changed1 schema field changed
    • addedInput schema / properties / company_id
      Added value: +{
+  "description": "Filter by company ID. Omit for all accessible companies.",
+  "type": "number"
+}
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so there is no contradiction. The description adds some context around candidate embedding but doesn't disclose pagination behavior, return format, or timestamp semantics beyond the schema's `updated_after` hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the core operation front-loaded. The `include=candidate` example adds practical value without wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool has 11 optional parameters and no output schema, so the description needs to cover pagination and return shape to be safely callable. It addresses filters and one include use case but leaves the agent guessing about paging, company scoping, and how to distinguish this from the candidate-specific sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 36%, so the description partially compensates by mapping filter dimensions like job, application, candidate, interviewer, date, and timestamps to likely parameters, and by explaining `include=candidate`. However, `page`, `size`, and `company_id` remain unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the operation ('List') and resource ('interviews'), and enumerates the filter dimensions. However, it doesn't explicitly differentiate this from the sibling `hires_list_candidate_interviews`, so it falls one step short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete agenda-widget use case and implies this is the tool for filtered interview listing. But it doesn't state when not to use it or point to alternatives like `hires_list_candidate_interviews`, so usage guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 100Hires - AI ATS & Recruitment Software toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources