Skip to main content
Glama
Ritesh-sudo

Job Search MCP Server

by Ritesh-sudo

search_ai_ml_jobs

Find AI and machine learning jobs and internships by location and keywords across multiple job platforms.

Instructions

Search for AI/ML internships and full-time roles across multiple job sites

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoJob location (e.g., "Remote", "San Francisco, CA", "New York, NY")Remote
maxResultsNoMaximum number of results to return
includeInternshipsNoInclude internship positions
includeFullTimeNoInclude full-time positions
keywordsNoAdditional keywords to search for (e.g., ["machine learning", "deep learning", "NLP"])

Implementation Reference

  • The primary handler function for the 'search_ai_ml_jobs' tool. It extracts parameters from args, creates a JobFilter tailored for entry-level AI/ML jobs requiring Python, calls JobSearchService.searchAllSites, and returns the results as JSON text.
    private async searchAIMLJobs(args: any) {
      const {
        location = 'Remote',
        maxResults = 50,
        includeInternships = true,
        includeFullTime = true,
        keywords = []
      } = args;
    
      const filter: JobFilter = {
        location,
        maxResults,
        includeInternships,
        includeFullTime,
        keywords,
        experienceLevel: 'entry', // Less than 1 year
        requiredSkills: ['python'],
        jobTypes: ['ai', 'ml', 'machine learning', 'artificial intelligence', 'data science']
      };
    
      const results = await this.jobSearchService.searchAllSites(filter);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(results, null, 2)
          }
        ]
      };
    }
  • JSON schema defining the input parameters for the 'search_ai_ml_jobs' tool, including location, maxResults, includeInternships, includeFullTime, and keywords.
    inputSchema: {
      type: 'object',
      properties: {
        location: {
          type: 'string',
          description: 'Job location (e.g., "Remote", "San Francisco, CA", "New York, NY")',
          default: 'Remote'
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of results to return',
          default: 50
        },
        includeInternships: {
          type: 'boolean',
          description: 'Include internship positions',
          default: true
        },
        includeFullTime: {
          type: 'boolean',
          description: 'Include full-time positions',
          default: true
        },
        keywords: {
          type: 'array',
          items: { type: 'string' },
          description: 'Additional keywords to search for (e.g., ["machine learning", "deep learning", "NLP"])',
          default: []
        }
      },
      required: []
    }
  • src/index.ts:37-73 (registration)
    Registration of the 'search_ai_ml_jobs' tool in the tools list returned by ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'search_ai_ml_jobs',
      description: 'Search for AI/ML internships and full-time roles across multiple job sites',
      inputSchema: {
        type: 'object',
        properties: {
          location: {
            type: 'string',
            description: 'Job location (e.g., "Remote", "San Francisco, CA", "New York, NY")',
            default: 'Remote'
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of results to return',
            default: 50
          },
          includeInternships: {
            type: 'boolean',
            description: 'Include internship positions',
            default: true
          },
          includeFullTime: {
            type: 'boolean',
            description: 'Include full-time positions',
            default: true
          },
          keywords: {
            type: 'array',
            items: { type: 'string' },
            description: 'Additional keywords to search for (e.g., ["machine learning", "deep learning", "NLP"])',
            default: []
          }
        },
        required: []
      }
    },
    {
  • Helper method in JobSearchService that performs parallel searches across all configured job scrapers (LinkedIn, Indeed, etc.) using the provided filter, aggregates results, and returns a comprehensive JobSearchResponse.
    async searchAllSites(filter: JobFilter): Promise<JobSearchResponse> {
      const startTime = Date.now();
      const results: JobSearchResult[] = [];
      
      // Search all sites in parallel
      const searchPromises = Array.from(this.scrapers.keys()).map(async (site) => {
        try {
          const result = await this.searchSite(site, filter);
          return result;
        } catch (error) {
          return {
            site,
            jobs: [],
            totalFound: 0,
            searchTime: 0,
            error: error instanceof Error ? error.message : 'Unknown error'
          };
        }
      });
    
      const searchResults = await Promise.all(searchPromises);
      results.push(...searchResults);
    
      const totalJobs = results.reduce((sum, result) => sum + result.jobs.length, 0);
    
      return {
        results,
        totalJobs,
        searchTimestamp: new Date().toISOString(),
        filters: filter
      };
    }
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 mentions searching 'across multiple job sites', which hints at aggregation behavior, but fails to detail critical aspects like rate limits, authentication needs, result format, pagination, or error handling for a search 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 a single, efficient sentence that front-loads the core purpose without unnecessary elaboration. Every word contributes directly to understanding the tool's function, making it highly concise and well-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 complexity of a search tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, result format, and usage guidelines, leaving significant gaps for an AI agent to operate effectively.

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%, providing full parameter documentation. The description adds no additional semantic context beyond the schema, such as explaining interactions between parameters (e.g., how 'keywords' refine searches). Baseline 3 is appropriate as the schema handles the heavy lifting.

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 verb 'search' and the resource 'AI/ML internships and full-time roles across multiple job sites', making the purpose evident. However, it doesn't explicitly differentiate from the sibling tool 'search_specific_job_site', which might handle single-site searches versus this multi-site approach.

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 alternatives, such as the sibling 'search_specific_job_site'. It lacks context on prerequisites, exclusions, or comparative scenarios, leaving the agent without clear usage direction.

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/Ritesh-sudo/MCPJobSearch'

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