Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_interview

Modify a scheduled interview's time, interviewers, location, or video link. Use the interview ID to correct scheduling details and replace panel members.

Instructions

Update a scheduled interview's time, interviewers, or location. Write operation.

To find interview_id: list_interviews_for_application on the candidate's app. For new interviewer_ids: list_users → match by name. When replacing interviewers, existing panel members keep their RSVP; new ones start as needs_action.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "interview_id": "<interview_id>"
    },
    "name": "update_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoNew end time as ISO 8601
startNoNew start time as ISO 8601
locationNoNew location or meeting link
interview_idYesScheduled interview ID to update
interviewer_idsNoReplaces all interviewers — provide the full list
video_conferencing_urlNoNew video call join URL

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • addedInput schema / properties / end / description
      Added value: +"New end time as ISO 8601"
    • addedInput schema / properties / interview_id / description
      Added value: +"Scheduled interview ID to update"
    • addedInput schema / properties / interviewer_ids / description
      Added value: +"Replaces all interviewers — provide the full list"
    • addedInput schema / properties / location
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "New location or meeting link",
+  "title": "Location"
+}
    • addedInput schema / properties / start / description
      Added value: +"New start time as ISO 8601"
    • addedInput schema / properties / video_conferencing_url
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "New video call join URL",
+  "title": "Video Conferencing Url"
+}
  2. Addedv0.3.4

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral load, and it does flag 'Write operation' plus a genuinely non-obvious side effect: replacing interviewers preserves existing members' RSVPs while new ones start as needs_action. It omits other write-relevant traits such as auth requirements, whether unspecified fields are left unchanged, and whether time changes re-notify participants.

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-loads the core action and write nature in the first sentence, then adds only actionable lookup and side-effect notes. No filler, though the two-line dependency hints are slightly terse.

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?

An output schema exists, so return values need not be explained. For a 6-param unannotated mutation tool, the description covers the key lookup paths and the interviewer RSVP behavior; only partial-update and permission semantics remain implicit.

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 the baseline is 3. The description reinforces the destructive replacement semantics of interviewer_ids and the ISO 8601 time fields, but adds little beyond what the schema already documents.

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?

States a specific verb (Update) and resource (scheduled interview) and enumerates the mutable fields (time, interviewers, location). The agent can immediately distinguish it from create_interview/delete_interview/get_interview without opening the schema.

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

Usage Guidelines4/5

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

Provides concrete prerequisite workflows: use list_interviews_for_application to obtain interview_id, and list_users to resolve interviewer_ids. It gives clear context for correct invocation but offers no explicit when-not guidance or routing between sibling update tools.

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