Skip to main content
Glama

AceRound AI Interview Copilot

generate_interview_experience

Write up an interview experience post (the questions the interviewer asked) from a live interview record, save it to the record, and return it; an existing write-up is replaced. Only live interviews of at least 5 minutes qualify. (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": "generate_interview_experience"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYesInterview id from list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations it discloses real behavior: the result is persisted to the record, an existing write-up is overwritten, and the call needs an interviews:write sign-in scope. The overwrite semantics are slightly at odds with destructiveHint=false, but it is an in-place regeneration rather than a deletion, so this is tension rather than a contradiction; it also doesn't say whether generation is synchronous or slow.

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?

Front-loaded with the action and artifact, then side effects, then eligibility, then auth — nothing is padded. The single long semicolon-and-parenthetical sentence is dense, but every clause carries distinct information.

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 one-parameter mutation tool with no output schema, it covers artifact, persistence, overwrite behavior, eligibility, and auth. What remains thin is failure handling (what happens for a short or non-live interview) and the shape of the returned write-up, which is only implied by 'return it'.

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% and the interviewId description already points at list_interviews, so the schema does the work. The description reinforces that the id must refer to a live interview of at least 5 minutes, which adds eligibility meaning, but adds no format or sourcing detail beyond the schema.

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?

States a specific verb and artifact: write up an interview experience post (the questions the interviewer asked) from a live interview record, save it to the record, and return it. That is clearly distinct from a transcript or report artifact, though no sibling is named explicitly to route the agent away from alternatives.

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 qualifying condition — only live interviews of at least 5 minutes qualify — plus the required auth scope, which is enough context to decide applicability. It stops short of naming a sibling to use instead when the interview is a mock, too short, or already has a write-up the user wants to keep.

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