Skip to main content
Glama

面灵AI 面试助手

list_interview_targets

Read-only

列出用户已保存的面试岗位(公司 + 岗位名),发起面试 / 模拟面试时需要其中一个岗位 ID。每行一个,新的在前。(需要用户授权,范围 interviews:read)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing an authorization requirement with a specific scope (interviews:read) and the ordering guarantee (新的在前), plus the per-line output shape — details annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence plus a parenthetical auth note; the resource and its downstream use are front-loaded, and every clause (fields returned, ID needed for interviews, ordering, auth scope) carries information an agent would otherwise lack.

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 zero-parameter, no-output-schema list tool this is nearly complete: it covers what is returned, row format, sort order, prerequisite authorization and why the result matters. Only minor gaps remain, such as the empty-list case or whether results are capped, which an agent might want to know.

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?

There are zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly does not invent parameter details.

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 description gives a specific verb and resource ('列出用户已保存的面试岗位'), specifies the returned fields (company + job title), and ties the output to a concrete downstream action (obtaining a 岗位 ID to start an interview or mock interview). An agent can distinguish this from create_interview_target or list_interviews without opening any schema.

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?

It explicitly states the context that selects this tool: you need one of these 岗位 IDs before 发起面试 / 模拟面试. It does not name alternative or sibling tools (e.g. create_interview_target, list_interviews) or exclusions, so it stops short of full alternative routing, but the when-to-use condition is unambiguous.

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