BambooHR MCP Server and API by Cotlet

List employees in BambooHR

bamboohr_list_employees

Read-onlyIdempotent

List employees in the user's own BambooHR account from ChatGPT, Claude or any AI agent. Returns how to do it in BambooHR step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's BambooHR Cloud Browser. BambooHR's official API: Yes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bamboohr_list_employees"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses that the tool opens nothing by itself and that its return value is a UI procedure with screens, buttons, and fields. The trailing 'BambooHR's official API: Yes' is ambiguous — it reads like API metadata rather than behavior, and could mislead an agent into thinking data is fetched via API.

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 behavioral core is front-loaded and sized appropriately for a zero-param guide tool. 'from ChatGPT, Claude or any AI agent' is filler, and the dangling 'BambooHR's official API: Yes' adds noise rather than information.

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?

There is no output schema, so the description must describe what comes back — and it does, specifying a step-by-step screen/button/field procedure. Combined with the explicit hand-off to the browser tools, an agent has enough to call it correctly; the ambiguous API line is the only loose end.

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?

The tool takes zero parameters, so the baseline is 4, and nothing in the description suggests hidden inputs. No parameter meaning is needed, and none is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (list employees in BambooHR) and then clarifies the actual mechanic: it returns step-by-step UI instructions rather than data. It distinguishes itself from the cotlet_browser_* siblings by naming them as the execution path, though it does not differentiate from other bamboohr_* siblings like bamboohr_get_report.

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?

It gives a clear use context and an explicit follow-on workflow: call this to get the procedure, then perform it with the cotlet_browser_* tools in the user's BambooHR Cloud Browser. There are no exclusion conditions (when not to use this versus a direct-report sibling), which keeps it short of a 5.

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

All BambooHR MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?