Skip to main content
Glama

interview_info

Retrieve interview details by ID to track candidate progress and coordinate hiring stages within the Ashby ATS.

Instructions

Get details of a single interview by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe interview ID

Implementation Reference

  • Registration of the 'interview_info' tool definition.
    types.Tool(
        name="interview_info",
        description="Get details of a single interview by ID.",
        inputSchema={
            "type": "object",
            "properties": {
                "id": {"type": "string", "description": "The interview ID"},
            },
            "required": ["id"],
        },
    ),
  • The 'handle_call_tool' function acts as a dynamic handler that routes the tool call to the corresponding Ashby API endpoint defined in TOOL_ENDPOINT_MAP.
    @server.call_tool()
    async def handle_call_tool(name: str, arguments: dict[str, Any]) -> list[types.TextContent]:
        """Route tool calls to the correct Ashby endpoint, passing arguments directly."""
        endpoint = TOOL_ENDPOINT_MAP.get(name)
        if not endpoint:
            return [types.TextContent(type="text", text=f"Unknown tool: {name}")]
    
        try:
            # Pass arguments straight through -- tool schemas already use Ashby's
            # camelCase param names so no translation is needed.
            response = ashby.post(endpoint, data=arguments if arguments else None)
            return [types.TextContent(type="text", text=json.dumps(response, indent=2))]
  • TOOL_ENDPOINT_MAP maps the 'interview_info' tool name to the '/interview.info' Ashby API endpoint.
    TOOL_ENDPOINT_MAP = {
        "job_list": "/job.list",
        "job_info": "/job.info",
        "job_search": "/job.search",
        "candidate_list": "/candidate.list",
        "candidate_search": "/candidate.search",
        "candidate_info": "/candidate.info",
        "candidate_create": "/candidate.create",
        "candidate_create_note": "/candidate.createNote",
        "candidate_list_notes": "/candidate.listNotes",
        "candidate_add_tag": "/candidate.addTag",
        "candidate_tag_list": "/candidateTag.list",
        "application_list": "/application.list",
        "application_info": "/application.info",
        "application_create": "/application.create",
        "application_change_stage": "/application.change_stage",
        "interview_stage_list": "/interviewStage.list",
        "interview_plan_list": "/interviewPlan.list",
        "interview_list": "/interview.list",
        "interview_info": "/interview.info",
        "department_list": "/department.list",
        "user_list": "/user.list",
        "source_list": "/source.list",
        "archive_reason_list": "/archiveReason.list",
        "location_list": "/location.list",
    }

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/PlenishAI/mcp-ashby'

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