Skip to main content
Glama
Ownership verified

Server Details

Ask Personio Recruiting the recruiting-ops questions dashboards miss by connecting applications, stage transitions, candidates, recruiting jobs, categories, org units, workplaces, jobs catalog, webhooks, event activity, and intake documents. Find stage-movement stalls, candidate freshness gaps, source quality by job/category, hiring load by department and workplace, webhook delivery issues, intake readiness gaps, and bottleneck owners. No dashboard build. No SQL.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsC

Average 2.9/5 across 30 of 30 tools scored. Lowest: 1.7/5.

Server CoherenceA
Disambiguation4/5

Most tools target specific entities and actions, but the generic api_request tool overlaps with many endpoints, potentially causing confusion. Additionally, similar-sounding tools like get_application and list_applications are clearly distinct, so the impact is limited.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with underscores (e.g., create_recruiting_application, list_applications, get_candidate). There are no mixed conventions or ambiguous abbreviations, making the naming predictable and clear.

Tool Count4/5

With 30 tools, the server covers a broad domain including applications, candidates, jobs, webhooks, and organizational entities. While slightly heavy, each tool serves a distinct purpose and the count is justified given the scope.

Completeness3/5

The tool set is read-heavy, with get and list operations for most entities, but missing update and delete for core recruiting resources (applications, candidates). This gaps agents from performing full lifecycle management without resorting to the generic api_request.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources