Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_interviews

List scheduled interviews across all applications, filtered by job, status, or date range. Read-only; retrieve interview details, interviewers, and organizers.

Instructions

List scheduled interviews across all applications. Read-only.

Each interview has id, application_id, job_id, starts_at/ends_at (or all_day_start_on/all_day_end_on), status, location, video_conferencing_url, plus (with include_details) interview {id, name}, interviewers [{id, name, email, response_status, scorecard_id}] and organizer. For a specific candidate's interviews, use list_interviews_for_application (search_candidates_by_name → list_applications(candidate_id=...) → match the application → use its ID).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPass next_cursor from the previous response to get the next page
job_idNoOnly interviews on this job — get ID from list_jobs
statusNoFilter by status, e.g. 'scheduled', 'awaiting_feedback', 'complete', 'to_be_scheduled'
paginateNo'single' for one page, 'all' to auto-fetch every pagesingle
per_pageNoResults per page (max 500)
starts_afterNoISO 8601 datetime — only interviews starting at/after this
created_afterNoISO 8601 datetime — only interviews created at/after this
starts_beforeNoISO 8601 datetime — only interviews starting before this
created_beforeNoISO 8601 datetime — only interviews created before this
include_detailsNoResolve interview name, interviewers and organizer (extra calls)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.5.0
    • addedInput schema / properties / created_after / description
      Added value: +"ISO 8601 datetime — only interviews created at/after this"
    • addedInput schema / properties / created_before / description
      Added value: +"ISO 8601 datetime — only interviews created before this"
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pass next_cursor from the previous response to get the next page",
+  "title": "Cursor"
+}
    • addedInput schema / properties / include_details
      Added value: +{
+  "default": true,
+  "description": "Resolve interview name, interviewers and organizer (extra calls)",
+  "title": "Include Details",
+  "type": "boolean"
+}
    • addedInput schema / properties / job_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only interviews on this job — get ID from list_jobs",
+  "title": "Job Id"
+}
    • removedInput schema / properties / page
      Removed value: -{
-  "default": 1,
-  "title": "Page",
-  "type": "integer"
-}
    • addedInput schema / properties / paginate / description
      Added value: +"'single' for one page, 'all' to auto-fetch every page"
    • addedInput schema / properties / per_page / description
      Added value: +"Results per page (max 500)"
    • addedInput schema / properties / starts_after
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 datetime — only interviews starting at/after this",
+  "title": "Starts After"
+}
    • addedInput schema / properties / starts_before
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 datetime — only interviews starting before this",
+  "title": "Starts Before"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by status, e.g. 'scheduled', 'awaiting_feedback', 'complete', 'to_be_scheduled'",
+  "title": "Status"
+}
  2. Addedv0.3.4

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavior burden. It does declare 'Read-only' and discloses that include_details triggers 'extra calls,' which is useful cost context for a read tool. However it says nothing about auth/permission requirements or rate-limit behavior, leaving meaningful gaps for a tool with zero annotation coverage.

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

Conciseness4/5

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

Front-loaded purpose and the read-only qualifier lead, with field details and the sibling routing following. It is somewhat dense, and the field enumeration slightly overlaps what the output schema already covers, but no sentence is wasted.

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

Completeness4/5

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

Given the output schema exists, return values need not be spelled out, yet the description still summarizes them helpfully. Combined with read-only disclosure and sibling routing, it is nearly complete; auth/permission expectations are the one notable omission.

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 100%, so all ten parameters are already documented in the schema, establishing a baseline of 3. The description adds the include_details return-shape effect (resolving interview name, interviewers, organizer), but that largely restates the schema's own note, so no credit above baseline.

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

Purpose5/5

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

Opens with a specific verb and resource plus scope: 'List scheduled interviews across all applications.' It explicitly contrasts itself with list_interviews_for_application, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

It names the alternative (list_interviews_for_application) and the exact condition that selects it (a specific candidate's interviews), even sketching the multi-step lookup path. That is explicit when-to-use and when-to-use-something-else guidance.

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

Deploy Server

Other Tools