Skip to main content
Glama

update_job_hunt

Modify job search settings and filters to refine automated job matching and application criteria, including titles, locations, salary ranges, and auto-apply preferences.

Instructions

Update job hunt settings and search filters. Use this to change what jobs are matched. IMPORTANT: When updating config, you must pass the ENTIRE config object as it replaces the existing config (not a partial merge). Use get_job_hunt first to see current config, then include all fields you want to keep.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe job hunt ID
nameNoNew name for the job hunt
autoModeNoEnable/disable full autopilot mode. When enabled, jobs are automatically matched, scored against your resume using AI, and applied to if they meet your minMatchScore threshold. Resume customization (if enabled) is applied before each application. Each auto-apply consumes a credit.
dailyLimitNoMaximum jobs to auto-apply per day (max: 100)
minMatchScoreNoMinimum match score for auto-apply (0-1). Default is 0.70 (70%) when not explicitly set.
customizeResumeNoEnable/disable AI resume customization for applications
statusNoJob hunt status
configNoSearch filters configuration. REPLACES entire config - include all fields you want to keep.

Implementation Reference

  • The handler implementation for update_job_hunt which parses input arguments, builds the update payload, calls the client, and returns the updated status.
    async (args) => {
      const updateData: Record<string, unknown> = {};
      if (args.name !== undefined) { updateData.name = args.name; }
      if (args.autoMode !== undefined) { updateData.autoMode = args.autoMode; }
      if (args.dailyLimit !== undefined) { updateData.dailyLimit = args.dailyLimit; }
      if (args.minMatchScore !== undefined) { updateData.minMatchScore = args.minMatchScore; }
      if (args.customizeResume !== undefined) { updateData.customizeResume = args.customizeResume; }
      if (args.status !== undefined) { updateData.status = args.status; }
      if (args.config !== undefined) { updateData.config = args.config; }
    
      if (Object.keys(updateData).length === 0) {
        return { content: [{ type: 'text' as const, text: JSON.stringify({ message: 'No fields provided to update' }, null, 2) }] };
      }
    
      await client.updateJobHunt(args.id, updateData);
      const updated = await client.getJobHunt(args.id);
      return { content: [{ type: 'text' as const, text: JSON.stringify({ message: 'Job hunt updated successfully', jobHunt: formatJobHunt(updated) }, null, 2) }] };
    }
  • The input validation schema for update_job_hunt defined using Zod.
    {
      id: z.string().describe('The job hunt ID'),
      name: z.string().optional().describe('New name for the job hunt'),
      autoMode: z.boolean().optional().describe('Enable/disable full autopilot mode. When enabled, jobs are automatically matched, scored against your resume using AI, and applied to if they meet your minMatchScore threshold. Resume customization (if enabled) is applied before each application. Each auto-apply consumes a credit.'),
      dailyLimit: z.number().optional().describe('Maximum jobs to auto-apply per day (max: 100)'),
      minMatchScore: z.number().optional().describe('Minimum match score for auto-apply (0-1). Default is 0.70 (70%) when not explicitly set.'),
      customizeResume: z.boolean().optional().describe('Enable/disable AI resume customization for applications'),
      status: z.enum(['ACTIVE', 'ARCHIVED', 'DELETED']).optional().describe('Job hunt status'),
      config: z.object({
        titles: z.array(z.string()).optional().describe('Job titles to match'),
        locations: z.array(z.string()).optional().describe('Locations to match. Use plain city names without state abbreviations (e.g., "San Francisco" not "San Francisco, CA"). For states, use the full state name (e.g., "Texas"). Use "Remote" to match remote jobs worldwide without country restrictions.'),
        countries: z.array(z.string()).optional().describe('Country codes'),
        companies: z.array(z.string()).optional().describe('Companies to include'),
        excludedCompanies: z.array(z.string()).optional().describe('Companies to exclude'),
        skills: z.array(z.string()).optional().describe('Required skills'),
        remote: z.boolean().optional().describe('When true, only return remote jobs. When false or omitted, return all jobs (both remote and non-remote).'),
        baseSalaryMin: z.number().optional().describe('Minimum salary'),
        baseSalaryMax: z.number().optional().describe('Maximum salary'),
        expLevels: z.array(z.string()).optional().describe('Experience levels (e.g., ["SE" for Senior, "MI" for Mid-level, "EN" for Entry])'),
        industries: z.array(z.string()).optional().describe('Industries (use get_industries to see valid values)'),
        companySize: z.array(z.string()).optional().describe('Company sizes (e.g., ["xs" for 1-50, "s" for 50-200, "m" for 200-1K, "l" for 1K-5K, "xl" for 5K+])'),
        h1bSponsorship: z.boolean().optional().describe('H1B sponsorship required'),
        relevancy: z.enum(['HIGH', 'MEDIUM']).nullable().optional().describe('Search relevancy mode - HIGH for strict title/skills matching, MEDIUM for broader keyword-based results. Default is null (MEDIUM behavior).'),
        dateOffset: z.enum(['24H', '1D', '2D', '7D', '14D', '1M', '3M', '6M', '9M', '1Y']).nullable().optional().describe('Only match jobs posted within this time window (e.g., "7D" for last 7 days). Default is "7D".'),
        workArrangement: z.array(z.string()).optional().describe('Work arrangement filter (e.g., ["Full Time", "Part Time", "Contract", "Internship", "Freelance", "Temporary"]). Defaults to ["Full Time"] if not set.'),
        excludedKeywords: z.array(z.string()).optional().describe('Keywords to exclude from job results'),
        excludedTitles: z.array(z.string()).optional().describe('Job titles to exclude from results'),
      }).optional().describe('Search filters configuration. REPLACES entire config - include all fields you want to keep.'),
  • The tool registration for update_job_hunt in the McpServer.
    server.tool(
      'update_job_hunt',
      'Update job hunt settings and search filters. Use this to change what jobs are matched. IMPORTANT: When updating config, you must pass the ENTIRE config object as it replaces the existing config (not a partial merge). Use get_job_hunt first to see current config, then include all fields you want to keep.',
Behavior4/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 effectively explains the critical behavioral trait that 'config replaces the existing config (not a partial merge)', which is essential for correct usage. However, it doesn't mention authentication requirements, rate limits, or error conditions that might be relevant for a mutation tool.

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 efficiently structured with three sentences that each serve a distinct purpose: stating the tool's purpose, explaining the replacement behavior, and providing procedural guidance. There's no wasted language, and the most critical information ('IMPORTANT' about replacement behavior) is appropriately emphasized.

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

Completeness4/5

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

For a mutation tool with 8 parameters, nested objects, and no annotations or output schema, the description provides good contextual completeness. It explains the critical replacement behavior and procedural requirements. However, it doesn't describe what happens on success/failure or return values, which would be helpful given the absence of an output schema.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal parameter-specific information beyond what's in the schema, mainly emphasizing the replacement behavior of the config parameter. This meets the baseline expectation when schema coverage is complete.

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 tool's purpose with specific verbs ('update job hunt settings and search filters') and resources ('job hunt'), and distinguishes it from sibling tools by explicitly mentioning get_job_hunt as a prerequisite. It goes beyond just restating the name to explain what the tool actually does.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('to change what jobs are matched') and includes crucial procedural instructions: 'Use get_job_hunt first to see current config, then include all fields you want to keep.' It also warns about the replacement behavior versus partial merge, which is essential usage guidance.

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