Skip to main content
Glama

面灵AI 面试助手

create_interview_target

新建一个面试岗位(公司 + 岗位名,可附岗位描述),返回岗位 ID,供发起面试使用。与网页端「新建岗位」相同。(需要用户授权,范围 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": {
      "name": "<name>"
    },
    "name": "create_interview_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes岗位名称
companyNameNo公司名称
descriptionNo岗位描述(JD),面试作答时作为背景

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?

Annotations only declare the safety profile (not read-only, not destructive, not open-world). The description adds genuinely non-redundant context: the required authorization and its scope (interviews:write), the fact that a position ID is returned, and that the JD is used as background during interview answering. It does not cover behavior on duplicate names or failure modes.

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 its fields, followed by return value, usage note, and auth scope in a compact parenthesis. Dense but every clause carries information; only the web-parity sentence is arguably decorative.

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 three-parameter create tool with no output schema, the definition covers what it makes, what it returns, required auth scope, and downstream use. Minor omissions (duplicate handling, whether the returned ID is required by start_interview) do not block correct invocation.

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%, so every parameter is already documented with constraints, and the description merely restates company/name/optional-JD in prose. The one value-add — that the description field serves as background context during interview answering — is already present in the schema description, so baseline 3 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 opens with a clear verb+resource ('新建一个面试岗位'), enumerates the constituent fields (company + job name, optional JD), and states the return value (岗位 ID). It is unambiguous what the tool creates, though it relies on the reader's understanding of the target/position concept rather than naming a sibling such as list_interview_targets for contrast.

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 tells the agent when this is needed: '供发起面试使用' — the prerequisite step before starting an interview — and anchors it to the equivalent web action ('与网页端「新建岗位」相同'). There is no explicit when-not guidance or named alternative for cases where a target already exists, which keeps it below a 5.

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