Skip to main content
Glama

teamtailor_get_candidate

Retrieve a candidate's details from Teamtailor by ID. Access specific candidate information for recruitment processes.

Instructions

Get a single candidate by their id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
candidateIdYes

Implementation Reference

  • Tool handler for teamtailor_get_candidate - receives candidateId, calls client.getCandidate, returns JSON response.
    server.tool(
      "teamtailor_get_candidate",
      "Get a single candidate by their id.",
      {
        candidateId: z.number(),
      },
      async ({ candidateId }) => {
        const candidate = await client.getCandidate(candidateId);
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(candidate),
            }
          ]
        }
      }
  • Zod schema for input validation - requires candidateId as a number.
    {
      candidateId: z.number(),
    },
  • src/server.ts:46-64 (registration)
    Tool registration using server.tool() with name 'teamtailor_get_candidate'.
    server.tool(
      "teamtailor_get_candidate",
      "Get a single candidate by their id.",
      {
        candidateId: z.number(),
      },
      async ({ candidateId }) => {
        const candidate = await client.getCandidate(candidateId);
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(candidate),
            }
          ]
        }
      }
    );
  • getCandidate method in TeamtailorClient - makes GET request to /candidates/{id} and returns the candidate data.
    async getCandidate(
      id: number,
    ): Promise<Candidate> {
      const url = new URL(`${this.baseUrl}/candidates/${id}`);
    
      const body = await this.request<{ data: Candidate }>(url);
      return body.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Get' with no details on response format, side effects, permissions, or rate limits. For a read operation, more context would be beneficial.

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?

The description is a single, front-loaded sentence with no superfluous words. It efficiently conveys the core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter tool and no output schema, the description is minimally complete. It states what the tool does but lacks details about the response or any edge cases, which could be helpful for a complete understanding.

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 coverage is 0%, and the description adds minimal meaning ('by their id') beyond the parameter name 'candidateId'. No format, constraints, or examples are given, but the purpose is partially clarified.

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 clearly states the action (Get), resource (candidate), and qualification (by id). However, it does not distinguish from sibling tool 'teamtailor_list_candidates' beyond the implied singular vs. plural.

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

Usage Guidelines3/5

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

The description implies that use is for retrieving a specific candidate by ID, but no explicit guidance on when to use this versus the list tool, or any prerequisites or alternatives.

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

Install Server

Other Tools

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/crunchloop/mcp-teamtailor'

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