Skip to main content
Glama

List open interview times

listInterviewSlots
Read-onlyIdempotent

The hiring manager's open times for a role in the candidate's interview process: three suggestions, how many times each day has, every time on one day when you pass day, the meeting types, and the booking form questions still open. Pass reschedule true to see times for moving a round already booked through Clera. Name the timezone when you offer times. bookInterview and rescheduleInterview take one start from here. Never show opportunityId.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "opportunityId": "<opportunityId>"
    },
    "name": "listInterviewSlots"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoYYYY-MM-DD in the candidate's timezone: lists every open time that day.
rescheduleNotrue for times to move the round already booked through Clera.
eventTypeSlugNoThe meeting type's slug, as listInterviewSlots listed it.
opportunityIdYesThe opportunityId of a process row from listMyPipeline.

Output Schema

NameRequiredDescriptionDefault
callYes
daysYes
hostYes
roleYes
roundYes
bookedYes
daySlotsYes
providerYes
timezoneYes
prefilledYes
suggestedYes
eventTypesYes
confirmsLaterYes
eventTypeSlugYes
openQuestionsYes
opportunityIdYes
timezoneSourceYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so the bar is lower. The description still adds valuable context by explaining what the response contains (three suggestions, daily counts, etc.) and includes a privacy note about data recording ('Clera privately records this tool's inputs and results').

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

Conciseness3/5

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

The first sentence is a very long, comma-separated list of return values that is hard to parse at a glance. While most sentences earn their place, the structure is dense and the privacy disclaimer at the end feels appended rather than integrated.

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?

With an output schema present, the description doesn't need to detail return values, but it does so anyway to help the agent understand the data. Combined with rich annotations, it provides nearly everything needed: when to use reschedule, how to handle timezones, and data-hiding instructions.

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%, meaning the schema already fully documents the parameters. The description reinforces a few details (e.g., using reschedule=true, passing a day to see times) but does not add meaning beyond what the schema provides. Baseline 3 is appropriate.

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 and resource ('open times for a role in the candidate's interview process'). It clearly distinguishes itself from siblings by explicitly naming how it relates to bookInterview and rescheduleInterview ('take one start from here').

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?

Provides explicit guidance on when to use the reschedule parameter ('Pass reschedule true to see times for moving a round already booked'). It also gives critical workflow instructions: 'Name the timezone when you offer times' and 'Never show opportunityId.'

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources