Skip to main content
Glama

List interview tracker updates from calendars

listTrackerUpdates
Read-onlyIdempotent

Read the interview tracker updates Clera found in the calendars your team connected (Integrations page, Google Calendar): interviews booked, moved, cancelled or already held with candidates in the pipeline.

Use it when the user asks to update their interview tracker, or what changed with their interviews. Each update has a plain label, the candidate, the role, the calendar event, and setInterviewArgs: the exact arguments for setInterview.

Never apply an update on your own. Show the user the list, ask which to apply, then call setInterview once per confirmed update with its setInterviewArgs. Scheduling or advancing sends the candidate prep reminders, so say that before they confirm.

An empty list means no calendar is connected or every interview already matches the tracker; point the user to the Integrations page if nobody connected a calendar yet.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listTrackerUpdates"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.

Output Schema

NameRequiredDescriptionDefault
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Beyond readOnlyHint, idempotentHint and openWorldHint=false, it discloses genuinely non-obvious behavior: an empty result has two distinct causes (no calendar connected vs. tracker already current), and applying an update later sends candidate prep reminders. The closing privacy/data-recording sentence is boilerplate that adds little decision value.

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?

It is front-loaded with what is read, then when to use it, then the mandatory human-confirmation workflow, then the empty-list edge case, which is the right order. The final sentence about private recording of inputs and results is boilerplate padding that displaces nothing but earns little.

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 read-only list tool with one optional parameter, an output schema, and full annotation coverage, everything an agent needs is present: trigger conditions, the shape of each returned update, the required confirmation step, the remediation for an empty list, and the downstream side effect of applying.

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?

There is a single parameter, orgId, whose meaning is fully documented in the schema (100% coverage). The description adds no interpretation of it — no note about when the org context matters — so the schema does all the work and the baseline 3 applies.

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?

The description names a specific verb and resource — reading interview tracker updates that Clera derived from connected Google calendars — and enumerates the concrete update kinds (booked, moved, cancelled, already held) scoped to candidates in the pipeline. That is enough for an agent to distinguish it from setInterview, which appears later as the apply step.

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 states the triggering user intents ('update their interview tracker' or 'what changed with their interviews'), forbids autonomous application, prescribes the confirm-then-call-single-update sequence, and names setInterview as the follow-up action with its parameter source (setInterviewArgs). The only alternative left implicit is listInterviewRequests, which is not this tool's job to route.

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