Skip to main content
Glama

List interview invitations

listInterviewRequests
Read-onlyIdempotent

The candidate's interview invitations: pending ones waiting for a yes or no, and the history of accepted and declined ones. acceptInterview and declineInterview act on a pending row by its interviewProgressId. Never show the id.

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": "listInterviewRequests"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
historyYes
pendingYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses that both pending and historical records are returned together, that rows carry an interviewProgressId which must not be surfaced, and that inputs and results are privately recorded for usage tracking and support.

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?

Two compact paragraphs: the scope first, then the sibling routing and the display rule. The closing data-recording sentence is somewhat boilerplate but does carry a genuine privacy disclosure, so it earns most of its space.

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 zero-parameter read tool with full annotation coverage and an output schema, nothing an agent needs is missing. Scope, sibling routing, id-handling, and data-recording behavior are all stated, so the return shape can be left to the output schema.

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?

With zero parameters there is nothing to disambiguate, so the baseline is high. The only identifier mentioned, interviewProgressId, is explicitly attributed to acceptInterview/declineInterview rather than to this tool, which avoids confusion about how to invoke it.

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 the exact resource (the candidate's interview invitations) and splits it into two precise scopes: pending rows awaiting a yes/no, and the history of accepted/declined ones. It also names the siblings that act on those rows (acceptInterview, declineInterview), so an agent can separate listing from acting without opening a 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?

It routes clearly: use this to view invitations, and use acceptInterview/declineInterview to act on a pending row by its interviewProgressId, plus the display rule 'Never show the id.' What it lacks is any exclusion among the many other list* siblings (listOutreachRequests, listInterviewSlots, etc.), so the boundaries are clear only for the accept/decline pair.

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