Skip to main content
Glama
jhgaylor

HireBase MCP Server

by jhgaylor

get_job

Retrieve detailed information about a specific job using its unique identifier.

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' - decorated with @mcp.tool(), calls _get_job_logic to retrieve job details by ID.
    @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)
  • The internal logic function _get_job_logic that performs the actual HTTP GET request to HireBase API /jobs/{job_id}.
    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)}
  • src/server.py:200-200 (registration)
    The @mcp.tool() decorator on the get_job function registers it as an MCP tool named 'get_job'.
    @mcp.tool()
  • Helper function that builds request headers (including API key) used by _get_job_logic.
    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?

No annotations are provided, so the description carries full burden. It mentions 'detailed information' but does not specify what fields are returned, any authentication or rate limits, or confirm it is a read-only operation. The description lacks sufficient behavioral context.

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 two short sentences with a structured Args section, no redundant words, and perfectly sized for the tool's simplicity.

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?

For a simple single-parameter get tool, the description is adequate but could be improved by noting what 'detailed information' includes, potential error conditions, or expected return format. Without annotations or output schema, additional context would enhance completeness.

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?

With 0% schema coverage, the description compensates by adding meaning: 'job_id: The unique identifier of the job' goes beyond the schema's title 'Job Id', explaining the parameter's role effectively.

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

Purpose5/5

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

The description clearly states the verb 'get' and the resource 'detailed information about a specific job', and the sibling tool 'search_jobs' implies this tool is for fetching a single job by ID, distinguishing it effectively.

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 usage for fetching a specific job by ID, but provides no explicit guidance on when to use it versus the sibling 'search_jobs', nor any exclusions or prerequisites.

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