Skip to main content
Glama

面灵AI 面试助手

get_interview_transcript

Read-only

读取某场面试的完整问答记录(面试官与用户的发言,按时间顺序,每次 80 条,用 offset 翻页)。(需要用户授权,范围 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_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
interviewIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish readOnly, non-destructive, closed-world behavior, so the lower bar applies. The description still adds real context beyond them: a page size of 80 items, offset-based pagination, chronological ordering, and an explicit OAuth-style scope requirement (interviews:read) that the annotations do not express.

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?

One compact, front-loaded sentence covers the resource, ordering, page size, pagination, and authorization with no filler. The nested parentheses make it slightly dense to parse, but nothing is redundant.

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 simple two-parameter read tool with no output schema, the description supplies what an agent actually needs to call it correctly: ordering, page size, pagination, and the required scope. The remaining gap, such as the shape of each returned utterance or what happens with an invalid or inaccessible interviewId, is minor but present.

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 description coverage is 0%, so the description must carry parameter meaning. It explains offset well, stating that results come 80 at a time and offset pages through them, which is information absent from the schema. It says little about interviewId beyond implying it identifies the interview, leaving format and provenance undocumented, so compensation is only partial.

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 pairs the specific verb 读取 with a precise resource, '某场面试的完整问答记录', and narrows it further to the utterances of the interviewer and the candidate in chronological order. That scope is clearly distinct from something like get_interview_report, though the description never names a sibling to contrast against explicitly.

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 implied: call this when you need the raw Q&A log of one interview. The auth requirement ('需要用户授权,范围 interviews:read') is a useful prerequisite, but there is no explicit when-not guidance and no named alternative such as the report tool for summarized output.

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