Skip to main content
Glama

AceRound AI Interview Copilot

set_live_interview_options

Change settings of the live interview in progress: recognition language (only within the set chosen at the start; the page reconnects once), auto-answer (when off, answers only on "Answer now"), and one card per question (follow-ups on the same question share one card). Auto-answer and one-card-per-question are supported only by the desktop app overlay. Pass only what should change. Requires the user to have this session open in the browser or desktop app and connected; the page carries it out exactly as if the user clicked the matching button. (Requires the user's sign-in with scope interviews:write.)

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

Input Schema

NameRequiredDescriptionDefault
langNoRecognition language
turnCardsNoOne card per question
autoAnswerNoAuto-answer

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?

Annotations only declare non-read-only and non-destructive; the description adds substantive behavior: the page reconnects once after a language change, the change is executed client-side 'exactly as if the user clicked the matching button', the user must have the session open and connected, and the interviews:write scope is required. These are the failure modes an agent actually needs.

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, then the three settings, then the constraints — a sensible ordering with no filler. Density of nested parentheses (especially the trailing requirement clause) makes it slightly harder to scan than a clean list.

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 three optional parameters, no output schema, and no destructive side effects, a caller needs to know patch semantics, per-parameter effects, platform limits, session prerequisites and auth scope — the description covers all of these. Nothing material is missing for correct invocation.

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 100%, so the baseline is 3, but the description goes further by explaining consequences of each flag: auto-answer off means answers only fire on an explicit 'Answer now', and turn-cards groups follow-ups onto one card. It does not enumerate the allowed language codes, but the schema's enum already does.

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?

The first clause gives a specific verb and resource — 'Change settings of the live interview in progress' — then enumerates the exactly three settings it controls (recognition language, auto-answer, card grouping). An agent can tell immediately this is a live-session configuration tool and not, e.g., a mock-interview or answer tool.

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?

Strong conditional guidance: 'Pass only what should change' establishes patch semantics, 'only within the set chosen at the start' bounds the language change, and the desktop-overlay restriction rules out ways of using this that would silently fail. It stops short of naming a sibling alternative for related needs (e.g. mock interview assist), which is the only gap.

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