Skip to main content
Glama

Move a booked interview

rescheduleInterview
Destructive

Move the interview round booked through Clera to a time from listInterviewSlots with reschedule true. The hiring manager and the candidate both get the updated invite, so the candidate gets one confirmation first. Only move it to a time the candidate picked. outcome rescheduled: done. pending: the scheduler confirms within minutes, so the old time stands until then. handoff: send the candidate handoffUrl; the old time stands until they finish there.

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>",
      "start": "<start>",
      "timeZone": "<timeZone>"
    },
    "name": "rescheduleInterview"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesOne start exactly as listInterviewSlots listed it.
timeZoneYesThe timezone exactly as listInterviewSlots named it.
opportunityIdYesThe opportunityId of a process row from listMyPipeline.
confirmRescheduleNoOnly when your client cannot show the confirmation prompt: "confirm" once the candidate has said yes to the new time, "cancel" otherwise. Never set it on your own.

Output Schema

NameRequiredDescriptionDefault
roleYes
labelYes
startYes
outcomeYes
handoffUrlYes
previousLabelYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false, openWorldHint=true) by disclosing side effects: both the hiring manager and candidate receive an updated invite, the candidate gets one confirmation first, and the old time stands during a pending or handoff state. It also states that inputs and results are privately recorded for support, which is a meaningful operational disclosure.

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?

The core rule (move only to a candidate-picked slot from listInterviewSlots) is front-loaded, and the outcome/pending/handoff clauses are terse. Sentences are fragmentary and 'with reschedule true' assumes the reader knows the listInterviewSlots field, but no sentence is redundant.

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

Completeness5/5

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

For a destructive, non-idempotent mutation with an output schema and fully documented parameters, the description covers the remaining burden: side effects on both parties, the transient pending state, and the handoff path. Nothing an agent needs to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds provenance constraints on 'start' (must be a time the candidate picked, taken from listInterviewSlots) that sharpen the field's meaning. It does not restate timeZone or opportunityId handling, leaving those entirely to the schema, which is acceptable.

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 ('Move the interview round booked through Clera') and pins the target time to a value obtained from listInterviewSlots, which distinguishes it from bookInterview and acceptInterview. An agent knows exactly which operation this performs 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 Guidelines5/5

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

Gives explicit preconditions and alternatives: the new time must come from listInterviewSlots, and it must be one the candidate picked. It also handles the branch cases (pending, handoff) with what to do in each, and the confirmReschedule constraint is scoped to clients that cannot show a prompt.

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