Skip to main content
Glama
huebnermarketing

keka-mcp-server

List Keka Employees

keka_list_employees
Read-onlyIdempotent

Retrieve a paginated employee list from Keka HRM. Filter by employment status, employee IDs, search key, probation, or notice period, and get details in markdown or JSON.

Instructions

Retrieve a paginated list of employees from Keka HRM.

Supports filtering by employment status, employee IDs, probation status, notice period, and a free-text search key.

Args:

  • employmentStatus (string, optional): Filter by status — 'Active', 'InActive', 'Terminated', 'NotJoined'

  • employeeIds (string, optional): Comma-separated employee IDs to fetch specific employees

  • searchKey (string, optional): Free-text search across name, email, employee number

  • inProbation (boolean, optional): Filter employees currently in probation

  • inNoticePeriod (boolean, optional): Filter employees in notice period

  • pageNumber (integer): Page number, starting at 1 (default: 1)

  • pageSize (integer): Results per page, max 200 (default: 100)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Paginated list of employees with ID, name, email, department, job title, status, and join date.

Examples:

  • List all active employees → employmentStatus='Active'

  • Find a specific person → searchKey='John Doe'

  • Get employees by IDs → employeeIds='emp1,emp2,emp3'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoResults per page (max 200)
searchKeyNoFree-text search across name, email, or employee number
pageNumberNoPage number (starts at 1)
employeeIdsNoComma-separated list of employee IDs
inProbationNoFilter for employees in probation
inNoticePeriodNoFilter for employees in notice period
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readablemarkdown
employmentStatusNoFilter by employment status

Schema Changelog

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

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety. The description goes beyond them by disclosing pagination behavior (page size max 200, start at 1), response_format choice, and the fields returned in the list.

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 longer than average but well structured: one-sentence summary, concise Args block, Returns line, and three examples. It is not bloated, though it does repeat some schema information.

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?

For an 8-parameter list tool with no output schema, this is complete: it covers all parameters, defaults, enums, return fields, pagination, and common use cases. An agent can select and invoke it correctly without opening the schema, which is unusually thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds value by grouping parameters, restating defaults in context, enumerating the employmentStatus options, and giving three concrete usage examples that map intents to parameter values.

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 first line uses a specific verb ('Retrieve') with a clear resource ('paginated list of employees from Keka HRM') and the filter list makes its scope obvious. This clearly differentiates it from sibling list tools (leave types, pay groups, departments) and from keka_get_employee.

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

Usage Guidelines4/5

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

The description gives clear context by specifying this is for paginated employee listing and provides three concrete examples mapping scenarios to parameter values. It does not explicitly contrast with keka_get_employee or state when-not-to-use, but the intended usage is clear enough to select among siblings.

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/huebnermarketing/keka-mcp'

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