MCP Teamtailor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAMTAILOR_URL | No | The URL of the Teamtailor API | https://api.teamtailor.com/v1 |
| TEAMTAILOR_API_KEY | Yes | Your Teamtailor API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| teamtailor_list_candidatesC | List and filter candidates. |
| teamtailor_get_candidateB | Get a single candidate by their id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves a single candidate by ID, the other lists and filters candidates. There is no ambiguity.
Both tools follow a consistent verb_noun pattern with the prefix 'teamtailor_', making them predictable and easy to understand.
With only 2 tools, the set feels thin for a typical ATS domain. While basic get and list are covered, a richer set (e.g., create, update, delete) is expected, making the count borderline.
The tool surface is severely incomplete for candidate management: it lacks create, update, delete operations, and other common entities like jobs or applications are missing.