Skip to main content
Glama
AndreyTepaykin

hh-mcp

by AndreyTepaykin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_manager_negotiations_statistics

Retrieve negotiation statistics for an hh.ru manager; omit employer_id or manager_id to resolve them from the authenticated account.

Instructions

Get negotiations statistics for a manager. employer_id/manager_id of the authenticated account can be omitted (resolved from /me). Requires HH_ACCESS_TOKEN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn the full raw hh.ru JSON instead of the compact summary.
manager_idNoId of the authenticated employer/manager; omit to resolve from /me. Do not pass 0.
employer_idNoId of the authenticated employer/manager; omit to resolve from /me. Do not pass 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.1.0
    • changedInput schema / properties / employer_id / description
      Previous value: -"Employer ID"New value: +"Id of the authenticated employer/manager; omit to resolve from /me. Do not pass 0."
    • changedInput schema / properties / employer_id / pattern
      Previous value: -"^\\d+$"New value: +"^[1-9]\\d*$"
    • changedInput schema / properties / manager_id / description
      Previous value: -"Manager ID"New value: +"Id of the authenticated employer/manager; omit to resolve from /me. Do not pass 0."
    • changedInput schema / properties / manager_id / pattern
      Previous value: -"^\\d+$"New value: +"^[1-9]\\d*$"
    • removedInput schema / required
      Removed value: -[
-  "employer_id",
-  "manager_id"
-]
  2. First observedv2.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the auth requirement ('Requires HH_ACCESS_TOKEN') and the /me resolution behavior, which is useful. However, it omits whether this is read-only, what the returned statistics contain, and any rate limits.

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?

Two compact sentences that front-load the purpose and then state the authentication requirement. No wasted words.

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

Completeness3/5

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

For a statistics-retrieval tool with no output schema, the description tells the agent what it gets and how to authenticate, but it doesn't explain the return shape or the distinction from the near-identical sibling get_negotiations_statistics, leaving a gap.

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?

All three parameters are already documented at 100% schema coverage, including the omit-to-resolve-from-/me behavior and the 'do not pass 0' constraint. The description largely repeats the schema's parameter notes rather than adding new meaning.

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?

States a specific verb and resource: 'Get negotiations statistics for a manager.' It's clear what the tool returns, though it doesn't distinguish itself from the similar sibling get_negotiations_statistics, which likely returns broader or differently-scoped statistics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the context (manager-scoped negotiation statistics) but never states when to use this versus get_negotiations_statistics or get_resume_negotiations_history. The reader must infer the distinction from the names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools