Skip to main content
Glama

面灵AI 面试助手

update_goal_hot_words

调整一个目标岗位的热词:hotWordIds 整体替换绑定的词库(最多 5 个,ID 取自 list_hot_word_libraries);customHotWords 整体替换自定义热词,或用 addCustomHotWords / removeCustomHotWords 增删个别词(最多 50 个)。未传的保持原样。(需要用户授权,范围 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": {
      "goalId": "<goalId>"
    },
    "name": "update_goal_hot_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes目标岗位 ID
hotWordIdsNo
customHotWordsNo
addCustomHotWordsNo
removeCustomHotWordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare it is not read-only, not destructive, and closed-world, so the baseline bar is lower. The description adds useful behavior beyond the annotations: it specifies full-replacement semantics, the cap of 5 library IDs and 50 custom words, and that the tool needs user authorization with the interviews:write scope. It does not explain what a full replacement discards from previous bindings or how errors are handled.

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?

The content is front-loaded, and each clause adds a distinct rule (replacement vs. incremental, caps, ID source, authorization). The single long sentence with multiple parenthesis groups is dense, but no sentence is wasted.

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 five-parameter mutation tool with no output schema, the description covers the semantics, caps, permission scope, and how unspecified fields behave. It leaves out what the call returns and what happens on permission or quota failures, both of which are secondary because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at only 20%, the description compensates well: it explains that hotWordIds and customHotWords replace the whole set, while addCustomHotWords and removeCustomHotWords change only the entries passed, and it gives the count caps and the constraint that omitted parameters leave state unchanged. This is meaning well beyond the terse schema.

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 names a specific verb and resource: it adjusts ('调整') the hot words of one target position ('目标岗位'). It also enumerates the fields it touches (hotWordIds, customHotWords, and add/remove variants), which sets it apart from sibling read or list tools such as get_goal_hot_words and list_hot_word_libraries. It never explicitly names the read or list counterpart as a starting point, so the intent is clear, but it would be clearer if it explicitly stated when to use it instead of those siblings.

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 gives concrete when-to guidance by contrasting full replacement for hotWordIds and customHotWords with incremental add/remove for individual words, and notes that unspecified fields remain unchanged. It also says where IDs come from (list_hot_word_libraries). It does not explicitly state when not to use this tool or what to do if the goal does not exist.

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