hibob-advanced-mcp

hibob_update_position_opening

Idempotent

Update an existing position opening's details, such as expected start date or recruitment status, by specifying the position and opening IDs with new field values.

Instructions

Change an existing opening, such as its expected start date or recruitment status.

Args: position_id: Parent position ID. opening_id: The opening's ID. fields: Flat mapping of field IDs to new values.

Returns: str: JSON confirming the update, or an error message beginning with "Error:".

Rate limit: 10 requests/minute.

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": {
      "position_id": "<position_id>",
      "opening_id": "<opening_id>",
      "fields": "<fields>"
    },
    "name": "hibob_update_position_opening"
  }
}

Input Schema

Name	Required	Description
`fields`	Yes	Fields to change, e.g. {"/positionOpening/recruitmentStatus": "onHold"}.
`opening_id`	Yes	ID of the opening to update.
`position_id`	Yes	Parent position ID.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations, the description discloses the return format ('JSON confirming the update, or an error message beginning with Error:') and the rate limit (10 requests/minute). It does not expand on side effects or permission needs, but the annotations already convey read/write and destructiveness signals.

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 description is compact and front-loaded with the core purpose, then follows a clear Args/Returns structure. The Args block is somewhat redundant with the schema, but overall it is efficient and readable.

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?

Combined with the rich input schema, output schema signal, and annotations, the description covers the key invocation details: parameters, return behavior, and rate limiting. It does not exhaustively list all updatable fields, but the examples plus open fields schema make the tool usable.

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 description coverage is 100%, so the baseline is 3. The description largely restates the parameter names and adds no significant meaning beyond the schema, though the schema's 'fields' example already provides formatting guidance.

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 action—'Change an existing opening'—and gives concrete examples of what can change ('expected start date or recruitment status'). This clearly distinguishes it from create, cancel, delete, and budget-related siblings.

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 phrase 'existing opening' implies the tool is for updating already-created openings, and the sibling names clarify lifecycle alternatives. However, the description does not explicitly state when to choose this over create_position_opening or delete_position_opening, nor does it mention any preconditions.

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

Deploy Server