Skip to main content
Glama

get_job_hunt

Retrieve detailed information about a specific job application using its unique ID to track progress and manage your job search effectively.

Instructions

Get details of a specific job hunt by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe job hunt ID

Implementation Reference

  • The MCP tool registration and handler implementation for "get_job_hunt". It uses the JobGPTApiClient to fetch the job hunt details and formats the output.
    server.tool(
      'get_job_hunt',
      'Get details of a specific job hunt by ID',
      {
        id: z.string().describe('The job hunt ID'),
      },
      async (args) => {
        const jobHunt = await client.getJobHunt(args.id);
        return { content: [{ type: 'text' as const, text: JSON.stringify(formatJobHunt(jobHunt), null, 2) }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets details' but doesn't clarify if this is a read-only operation, what details are returned, error handling, or any rate limits. This is inadequate for a tool with zero annotation coverage.

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, efficient sentence with no wasted words, clearly front-loading the core functionality. It's appropriately sized for a simple lookup tool.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what details are returned, potential errors, or behavioral traits, making it insufficient for an agent to fully understand the tool's operation beyond basic purpose.

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 meaning beyond the input schema, which has 100% coverage and fully documents the 'id' parameter. It implies the parameter is used to identify a specific job hunt, but doesn't provide additional context like format examples or constraints, meeting the baseline for high schema coverage.

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 details') and resource ('a specific job hunt by ID'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'get_job' or 'list_job_hunts', which would require specifying it retrieves a single job hunt entity by its identifier.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention using 'list_job_hunts' for multiple job hunts or 'get_job' for job details instead, leaving the agent to infer usage from the name alone.

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/6figr-com/job-gpt-mcp-server'

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