Skip to main content
Glama

AceRound AI Interview Copilot

retry_interview_report

Regenerate an interview report that failed to generate (when get_interview_report says it failed). Generation runs in the background for a minute or two; read it afterwards with get_interview_report. (Requires the user's sign-in with scope interviews:write.)

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

Input Schema

NameRequiredDescriptionDefault
interviewIdYesInterview id from list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that generation is asynchronous, takes a minute or two, requires the user's sign-in with the interviews:write scope, and that the result must be retrieved separately. These are exactly the behavioral facts an agent needs to avoid polling errors or auth failures. It does not state whether an existing report is overwritten, but that is a minor omission.

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 tight sentences with the trigger condition front-loaded and the async/auth caveats confined to a parenthetical. Every clause carries actionable information, though the nested parentheses make it slightly denser than necessary.

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 one-parameter tool with no output schema, the description covers the precondition, the async nature, the expected wait, the retrieval path, and the auth requirement. Nothing needed to call or follow up on this tool is missing.

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 coverage is 100% with a single interviewId parameter already documented as coming from list_interviews, so the schema carries the parameter burden. The description adds no further meaning about the id beyond what the schema provides, which is the baseline case.

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 (Regenerate) and resource (interview report), and narrows scope with the precondition 'that failed to generate'. It explicitly contrasts with get_interview_report, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives the exact trigger condition ('when get_interview_report says it failed') and the follow-up step ('read it afterwards with get_interview_report'). The implicit when-not (do not use for reports that generated successfully) is clear from the precondition.

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