Skip to main content
Glama

AceRound AI Interview Copilot

list_interviews

Read-only

List the user's interview sessions (live and mock), newest first, 20 per page. (Requires the user's sign-in with scope 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
pageNo
typeNoINTERVIEW = live interviews, MOCK_INTERVIEW = mock interviews; omit for both

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuine value with 'newest first', '20 per page', and the required auth scope 'interviews:read', but says nothing about total counts, whether more pages exist, or the shape of a returned session.

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?

One front-loaded sentence plus a short parenthetical; pagination, ordering, scope, and the auth requirement are all stated with no filler or repetition of the tool name.

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 simple two-parameter read tool with annotations covering the safety profile, the description supplies the key operational facts: page size, ordering, filter scope, and the required permission scope. The only gap is that with no output schema, an agent gets no hint about what fields a returned interview session contains.

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 only 50% — the `page` parameter has no description at all — so the description's '20 per page' and 'newest first' are what give that parameter meaning. The '(live and mock)' phrasing also reinforces the `type` enum semantics beyond the schema's own enum labels.

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 names a specific verb and resource ('List the user's interview sessions') and scopes it with '(live and mock)', which separates it from adjacent resources like interview targets or exams. It stops short of naming a sibling alternative explicitly, 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 Guidelines3/5

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

Usage is implied by the list semantics and the parenthetical '(live and mock)' hints that filtering is optional, but there is no explicit when-to-use statement, no when-not-to-use, and no pointer to a related tool for a different view of interview data.

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