Skip to main content
Glama

AceRound AI Interview Copilot

create_hot_word_library

Create a custom hotword library (name + words; up to 200 words per library and 20 libraries per user). Returns its ID; bind it to a role with update_goal_hot_words. (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": {
      "name": "<name>"
    },
    "name": "create_hot_word_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
wordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses real operational constraints an agent would otherwise learn only from an error: a 200-word cap per library, a 20-library cap per user, and the required OAuth scope (interviews:write). It also states the return value ('Returns its ID'), which the absent output schema would otherwise leave unknown.

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 front-loaded sentence with the action first, followed by limits, the next-step tool, and the auth note – nothing extraneous. The stacked parentheticals make it slightly dense, but every clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter create tool with no output schema, the description covers what is being created, quota limits, the return value, the follow-up binding step, and the required auth scope. An agent has everything needed to invoke it correctly on the first attempt.

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?

Schema coverage is 0%, so the description must carry the load, and it partly does: it names both fields and supplies the 200-words-per-library limit that the schema does not express anywhere. It omits the per-field constraints present in the schema (name 1-30 chars, each word max 50 chars), leaving some semantics to the schema's raw fields.

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 opens with a specific verb and resource ('Create a custom hotword library') and immediately names the composing fields, so it is unmistakable against siblings like update_hot_word_library, delete_hot_word_library, and list_hot_word_libraries. It also identifies the follow-up tool (update_goal_hot_words), which clarifies its place in the workflow.

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 clear forward guidance: after creation the library's ID must be bound to a role via update_goal_hot_words, which tells the agent the next call. It stops short of stating when NOT to create one (e.g., using suggest_hot_word_libraries to generate words first) or listing prerequisites, so it falls short of a full when/when-not treatment.

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