Skip to main content
Glama

AceRound AI Interview Copilot

export_interview_markdown

Read-only

Turn a full interview record (transcript and answer-assistant solutions) into tidy Markdown. Returns its length, outline, opening, and a download link for the full text. Takes a few dozen seconds. (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": "export_interview_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYesInterview id from list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, it discloses real operational traits: a latency expectation ('a few dozen seconds'), a required auth scope ('interviews:read'), and, importantly, that the call returns a summary plus a download link rather than the Markdown itself. That last point prevents a common misuse of a tool named 'export'. It does not say whether the generated file expires or is cached.

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?

Three short sentences, front-loaded with what the tool produces, followed by return shape, latency, and auth. No filler, though the parenthetical could be tightened.

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 still covers the return payload (length, outline, opening, download link), latency, and auth requirements. That is enough for an agent to call it correctly and set expectations.

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?

There is a single parameter at 100% schema coverage, and the schema already states it comes from list_interviews. The description adds nothing about the id format or behavior for unknown ids, so the baseline applies.

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?

The description states a specific verb and resource: 'Turn a full interview record (transcript and answer-assistant solutions) into tidy Markdown', and the parenthetical scope separates it from get_interview_transcript and from export_exam_markdown by resource type. It never explicitly names an alternative, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is only implied by the name and the 'full interview record' phrasing; there is no when-to-use/when-not statement and no pointer to get_interview_transcript for raw text. The auth-scope prerequisite is helpful context but not invocation guidance.

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