Skip to main content
Glama
AndreyTepaykin

hh-mcp

by AndreyTepaykin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_manager_resume_limits

Retrieve a manager's resume-view limits to interpret view counters and avoid misreading zeros or 404s as blocks. Requires HH_ACCESS_TOKEN.

Instructions

Informational resume-view limits for a manager (hh.ru counter may not match real views; 404/zeros are not a captcha signal). employer_id/manager_id of the authenticated account can be omitted (resolved from /me). Do not pass 0. 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

A3.6/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it delivers real behavioral context: the hh.ru counter may not match actual views, 404/zeros are not a captcha signal, auth requires HH_ACCESS_TOKEN, and IDs are resolved from /me. It omits return format and rate-limit behavior, keeping it out of 5 territory.

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?

Three dense, front-loaded clauses with no filler; the most important caveat (counter may not match real views) leads. Slightly telegraphic, but nothing is wasted.

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?

Covers auth, ID resolution, and interpretation caveats, which is strong for an unannotated tool. However, with no output schema it does not describe the shape of the limits returned, leaving an agent guessing at the response structure.

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% and the schema already documents 'omit to resolve from /me' and 'Do not pass 0' for both IDs, so the description largely restates structured data. The one added nuance is that either ID may be omitted for the authenticated account, but no new syntax or format detail is introduced.

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 resource (resume-view limits) and actor (manager), and frames it as informational, which distinguishes it from the nearby get_manager_negotiations_statistics. It does not explicitly name a sibling to route against, so it falls short of a 5.

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?

Provides context that this is informational and that IDs may be omitted, plus a 'Do not pass 0' caveat, but never says when to choose this tool over the many other manager/employer statistics tools. Usage is implied rather than directed.

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