Skip to main content
Glama

AceRound AI Interview Copilot

update_goal_hot_words

Adjust a target role’s hotwords: hotWordIds replaces the bound libraries (up to 5; IDs from list_hot_word_libraries); customHotWords replaces the custom words, or use addCustomHotWords / removeCustomHotWords for individual words (up to 50). Anything omitted stays unchanged. (Requires the user's sign-in with scope 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
goalIdYesTarget role ID
hotWordIdsNo
customHotWordsNo
addCustomHotWordsNo
removeCustomHotWordsNo

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 only declare non-read-only/non-destructive/non-open-world; the description adds the important behavioral facts: two fields overwrite existing bindings, capacity caps of 5 libraries and 50 words, a partial-update default, and the required sign-in scope interviews:write. It does not describe what the response contains after the update.

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 front-loaded paragraph where every clause carries information — scope, field semantics, limits, omission behavior, and auth. There is no filler or repetition.

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 mutation tool with annotations but no output schema, the description covers preconditions, overwrite semantics, limits, and partial-update behavior well. The only gap is what the call returns or how the resulting hotword state can be verified.

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?

With schema coverage at 20%, the description does the heavy lifting by explaining all four optional fields and where their values come from. The '(up to 50)' phrasing next to the custom word lists is ambiguous against the schema's per-item maxLength of 50, leaving an agent unsure whether 50 is a word count or a character limit.

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?

States a specific verb and resource ('Adjust a target role's hotwords') and immediately enumerates what can be changed, so an agent can distinguish it from get_goal_hot_words or match_goal_hot_words without opening the 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?

Explains the mode choice clearly: hotWordIds and customHotWords replace, while add/removeCustomHotWords edit individual entries, and 'anything omitted stays unchanged' resolves the partial-update question. It also points to list_hot_word_libraries as the ID source, though it does not say when to prefer add/remove over a full replace.

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