Skip to main content
Glama

AceRound AI Interview Copilot

get_interview_report

Read-only

Read the review report of one interview: summary, scores, strengths and weaknesses, suggestions, and each question with the answer, score, evaluation, and suggestion. Interview ids come from list_interviews. (Requires the user's sign-in with scope interviews:read.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "interviewId": "<interviewId>"
    },
    "name": "get_interview_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so safety is covered structurally. The description adds material context beyond that: the required sign-in and the 'interviews:read' scope, which an agent cannot infer from annotations or schema, plus a clear inventory of the returned data.

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?

Two compact sentences: the payload inventory is front-loaded on the verb+resource, and the id-source/auth notes follow as supporting detail. The long enumeration is dense but every item earns its place by telling the agent what it gets back.

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?

With no output schema, the description carries the burden of explaining return values and does so item by item; the sole parameter's origin and the auth requirement are both covered. What is absent — behavior when the report is not yet ready or failed, where retry_interview_report exists — is a minor edge case rather than a calling blocker, but it keeps this just at the threshold of complete.

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 0% for the single interviewId parameter, so the description must compensate — and it does by explaining that the id selects exactly one interview and where such ids originate (list_interviews). It does not describe the id's format or constraints (1-64 chars), but provenance guidance is the more useful part.

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 a specific verb and resource ('Read the review report of one interview') and then enumerates exactly what the report contains: summary, scores, strengths/weaknesses, suggestions, and per-question answer/score/evaluation/suggestion. That level of specificity also implicitly separates it from get_interview_transcript (raw transcript) and list_interviews (enumeration).

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?

Gives a concrete precondition for obtaining the required id ('Interview ids come from list_interviews'), which is the main routing decision an agent needs. It stops short of stating when not to use it — e.g. when a report has not yet been generated and retry_interview_report is the right call — so no exclusions are offered.

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