Skip to main content
Glama
jhgaylor

HireBase MCP Server

by jhgaylor

get_job

Retrieve detailed information about a specific job by providing its unique identifier. This tool helps users access comprehensive job data from the HireBase Job API.

Instructions

Get detailed information about a specific job

Args:
    job_id: The unique identifier of the job

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes

Implementation Reference

  • The MCP tool handler for 'get_job', registered via @mcp.tool() decorator. It receives the job_id parameter and delegates execution to the internal _get_job_logic helper.
    @mcp.tool()
    def get_job(job_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific job
    
        Args:
            job_id: The unique identifier of the job
        """
        return _get_job_logic(job_id=job_id)
  • Helper function implementing the core logic: makes HTTP GET request to HireBase API endpoint for the specific job_id, handles errors, and returns job details or error message.
    def _get_job_logic(job_id: str) -> Dict[str, Any]:
        """Internal logic for retrieving a specific job via HireBase API."""
        try:
            response = requests.get(
                f"{HIREBASE_API_BASE}/jobs/{job_id}", headers=get_hirebase_headers()
            )
            response.raise_for_status()
            return response.json()
    
        except requests.exceptions.RequestException as e:
            # Log the error or handle it as needed
            # print(f"HireBase API Error: {e}") # Example logging
            return {"error": str(e)}
  • Utility helper to generate headers for HireBase API requests, including optional API key.
    def get_hirebase_headers():
        """Get headers for HireBase API requests"""
        headers = {"Content-Type": "application/json"}
        if HIREBASE_API_KEY:
            headers["x-api-key"] = HIREBASE_API_KEY
        return headers
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed information' but lacks details on permissions, rate limits, error handling, or output format. The description is minimal and doesn't compensate for the absence of annotations.

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 description is concise and front-loaded, with the purpose stated clearly in the first sentence. The second sentence provides parameter information without unnecessary elaboration, though it could be more structured.

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

Completeness2/5

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

Given the absence of annotations and output schema, the description is incomplete. It covers the basic purpose and parameter but lacks details on behavior, output, or usage context, which are critical for a tool with no structured metadata.

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?

The description adds minimal parameter semantics: it explains that 'job_id' is 'The unique identifier of the job.' With 0% schema description coverage and 1 parameter, this provides basic meaning but doesn't fully compensate for the lack of schema details, such as format or constraints.

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 tool's purpose: 'Get detailed information about a specific job.' It uses a specific verb ('Get') and resource ('job'), though it doesn't explicitly differentiate from its sibling 'search_jobs' beyond the singular vs. plural distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus its sibling 'search_jobs.' It implies usage for a specific job via the 'job_id' parameter but offers no explicit alternatives, exclusions, or context for tool selection.

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/jhgaylor/hirebase-mcp'

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