Skip to main content
Glama
JustParent

hibob-advanced-mcp

by JustParent

hibob_search_positions

Read-onlyIdempotent

Search company positions by specifying fields and optional filters to retrieve matching entries, including raw IDs and readable labels for HR operations.

Instructions

Search the company's positions.

Returns one entry per matching position. Each entry has 'values' (the raw values, including the IDs needed by the update tools) and 'display' (human-readable labels).

This endpoint has no pagination, so always request only the fields you need and filter where possible in a large organization.

Args: fields: Field IDs to return (1-50). filters: Optional filter clauses combined by HiBob. include_human_readable: Include display labels alongside raw values.

Returns: str: JSON of the form {"count": int, "entries": [{"values": {...}, "display": {...}}]}, or an error message beginning with "Error:".

Examples: - "Which positions are vacant?" -> fields=['/position/id', '/position/name'], filters=[{field_id: '/position/status', operator: 'equals', values: ['vacant']}] - Don't use when: you need opening-level detail such as expected start dates (use hibob_search_position_openings).

Rate limit: 100 requests/minute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesField IDs to return, 1-50 of them, e.g. ['/position/id', '/position/name', '/position/status'].
filtersNoOptional filters. Filterable fields: '/position/status', '/position/name', '/position/hasOpenRequests', '/position/id'.
include_human_readableNoAlso return display labels for each value.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), the description discloses no pagination, rate limit of 100 requests/minute, and the response shape with values/display, including that values carry IDs needed by update tools. This gives agents actionable expectations for invocation.

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?

Well-sectioned with opening, return format, warning, args, returns, example, and rate limit. The Args section somewhat duplicates schema, but the overall structure is clear and front-loaded with key behavioral caveat (no pagination) early.

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?

Given rich annotations, complete schema, and the description's own return-shape and example, an agent can correctly invoke it, including constructing valid filters. It even covers rate limiting and differentiates from the closest sibling. Nothing essential is missing.

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 schema already documents fields, filters, and include_human_readable. The description adds a concrete filter example ('Which positions are vacant?') and notes filters are combined by HiBob, a slight semantic addition, but largely restates parameter meaning. Baseline 3 is appropriate.

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 clear verb+resource: 'Search the company's positions.' It distinguishes from siblings by specifying one entry per matching position and explicitly contrasts with hibob_search_position_openings. No ambiguity about what resource is queried.

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

Usage Guidelines5/5

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

Explicitly says 'Don't use when: you need opening-level detail... (use hibob_search_position_openings),' naming the alternative and the condition. It also advises requesting only needed fields and filtering in large organizations due to no pagination, which is practical usage context.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JustParent/hibob-advanced-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server