Skip to main content
Glama
mikkmihkel

BambooHR MCP Server

by mikkmihkel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List BambooHR users

bamboohr_list_users
Read-onlyIdempotent

Review BambooHR access by listing user accounts with employee id, status, and last login. Filter by status or name to find enabled accounts and users who never logged in.

Instructions

List BambooHR user accounts (people who can log in) with their linked employee id, status and last login (no email: BambooHR may return a home address there). Useful for access reviews: who has an enabled account, who never logged in. Narrow the list with status or search; more accounts than the per-call record limit are refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoCase-insensitive substring of the first or last name.
statusNoOnly accounts with this status. Default: all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.0
    • changedInput schema / properties / search / description
      Previous value: -"Case-insensitive substring of the first name, last name or email."New value: +"Case-insensitive substring of the first or last name."
  2. Changed1 schema field changedv4.1.0
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Case-insensitive substring of the first name, last name or email.",
+  "minLength": 1,
+  "type": "string"
+}
  3. First observedv3.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond annotations: it returns specific fields, flags the no-email caveat where BambooHR may return a home address, and states that accounts exceeding the per-call record limit are refused. It does not cover ordering or pagination, but for a list tool this is a solid disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: main function and return fields, use case, then filtering and a critical limit warning. The key purpose is front-loaded and no redundant prose is present.

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 a simple tool with two optional parameters and no output schema, the description covers the function, relevant fields, an important data caveat (no email), practical use, filtering options, and the record-limit refusal behavior. Nothing needed for correct invocation 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 both `search` and `status` are already documented in the input schema. The description only restates that filters exist ('narrow the list with status or search') without adding new semantic detail beyond the schema. 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?

The description states a specific verb ('List') and a distinct resource ('BambooHR user accounts (people who can log in)'), differentiating it from employee-list tools by focusing on login-capable accounts. It also lists returned fields (linked employee id, status, last login), making the tool's purpose unmistakable even without inspecting the schema.

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 concrete use context ('useful for access reviews'), explains how to narrow results ('with status or search'), and warns about the per-call record limit being refused. It does not explicitly name sibling alternatives or state when not to use this tool, so it stops short of full when/when-not guidance.

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