Skip to main content
Glama

AceRound AI Interview Copilot

list_interview_targets

Read-only

List the user's saved interview targets (company + role). Starting a live or mock interview needs one of these IDs. One per line, newest first. (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_interview_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description's job is to add context — and it does: output is one target per line, ordered newest first, and the call requires sign-in with the interviews:read scope. The remaining gap is what an empty result looks like, which matters for a discovery tool an agent may chain from.

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?

Four short sentences, front-loaded with purpose, then the dependency on start_interview, then output shape, then the auth note in parentheses. Nothing repeats the tool name or pads the definition.

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 zero-parameter list tool with no output schema, the description supplies what the schema cannot: ordering, line-per-item format, and the scope requirement. Only the empty-list case and the fallback to create_interview_target are unaddressed.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It correctly avoids inventing parameter behavior and instead spends its words on return shape and auth.

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?

"List the user's saved interview targets (company + role)" is a specific verb + resource, and the parenthetical defines what a target actually is. It does not explicitly distinguish itself from the sibling list_interviews or create_interview_target, so an agent must infer that this is the saved-target catalog rather than interview sessions.

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?

"Starting a live or mock interview needs one of these IDs" gives a clear precondition that tells the agent when this tool is the right first step. It stops short of stating what to do when the list is empty (e.g., point at create_interview_target), so no explicit alternative routing is provided.

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