Skip to main content
Glama

list_interviews

Read-onlyIdempotent

List your interview history with pagination and filters (metadata only: no transcripts, audio, or full reports). Requires interviews:read.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page of your interview history. Omit or use a nonpositive value for page 1. Follow the returned pagination instead of assuming the first page is complete.
sortNoUse oldest for ascending start time; newest, omitted, or another value retains the website's newest-first order.
limitNoInterviews per page. Omit or use a nonpositive value for 20; values above 100 are capped at 100.
searchNoOptional website-compatible title or scenario search, up to 200 Unicode characters. Ownership is always derived from the token; this is not a user or storage-key search.
statusNoOptional exact interview status, such as completed, paused, active, pending, interrupted, payment_revoked, or deletion_pending. Omit or use all for every status. A deletion_pending interview is unavailable for practice or report reads; retry its confirmed deletion to finish cleanup. This filters history and does not change interview state.

Output Schema

NameRequiredDescriptionDefault
dataYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds genuinely new context: the required authorization scope (interviews:read) and the explicit data boundary (no transcripts, audio, or full reports). It does not discuss result ordering defaults or page-completeness caveats itself, though the schema does.

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

Conciseness5/5

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

A single front-loaded sentence pairs the core action with the scope limitation, then appends the auth requirement as a compact clause. Every element earns its place with no redundant restatement of the title or schema.

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?

For a read-only list tool with zero required params, full schema coverage, annotations, and an output schema, the description covers purpose, data boundary, and auth. Nothing essential is missing for correct invocation, though a pointer to the sibling that should be used for reports/transcripts would close the last gap.

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% and all five parameters carry detailed semantic descriptions (page defaults, limit cap of 100, status enumeration, search scope), so the schema does the heavy lifting. The description only gestures at "pagination and filters" without adding syntax or behavior beyond what the schema already states, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("List your interview history") and bounds the scope precisely with "metadata only: no transcripts, audio, or full reports," which implicitly separates it from report/transcript-reading siblings. It stops short of naming the sibling tools an agent should use instead, so it is clear but not maximally differentiating.

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 supplies when-not guidance via the metadata-only exclusion, telling the agent this is not the tool for transcripts, audio, or full reports, and it states the required scope (interviews:read). It never explicitly names the alternative tools for those excluded cases, leaving the agent to infer routing from the exclusions.

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