Skip to main content
Glama

search_jobs

Search job listings using query and optional filters including tech stack, compensation, and remote preference.

Instructions

Search for job listings matching a query and optional filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesJob search query (e.g. 'Senior Backend Engineer')
stackNoTech stack filter (e.g. 'Node.js, TypeScript')
comp_minNoMinimum compensation in USD
comp_maxNoMaximum compensation in USD
remoteNoFilter for remote-only jobs
limitNoMax results to return (default: 10)

Implementation Reference

  • Schema definition for the search_jobs tool, including input properties (query, stack, comp_min, comp_max, remote, limit) and type/description metadata.
    const WEEK1_TOOLS = [
      {
        name: 'search_jobs',
        description: 'Search for jobs across integrated job boards. Returns ranked listings matching the query and optional filters.',
        inputSchema: {
          type: 'object',
          properties: {
            query: {
              type: 'string',
              description: 'Job title, keywords, or natural-language search (e.g. "senior backend engineer fintech")',
            },
            stack: {
              type: 'string',
              description: 'Comma-separated tech stack filter (e.g. "Node.js,TypeScript,PostgreSQL")',
            },
            comp_min: {
              type: 'number',
              description: 'Minimum annual compensation in USD',
            },
            comp_max: {
              type: 'number',
              description: 'Maximum annual compensation in USD',
            },
            remote: {
              type: 'boolean',
              description: 'If true, return only remote-friendly roles',
            },
            limit: {
              type: 'number',
              description: 'Max results to return (default: 20, max: 100)',
            },
          },
          required: ['query'],
        },
      },
  • index.js:239-242 (registration)
    Registration of search_jobs as a locally-defined new tool via WEEK1_TOOLS array, included in the NEW_TOOL_NAMES set for merging with backend tools.
    const NEW_TOOL_NAMES = new Set([
      ...WEEK1_TOOLS.map(t => t.name),
      ...WEEK2_TOOLS.map(t => t.name),
    ]);
  • The tools/call handler (handleToolsCall) that proxies the search_jobs invocation to the backend API via callBackend. If the backend is unreachable, it returns a stub 'not_implemented' response.
    async function handleToolsCall(id, params) {
      const toolName = params && params.name;
    
      try {
        const result = await callBackend({ jsonrpc: '2.0', id, method: 'tools/call', params });
        send({ ...result, id });
      } catch (err) {
        // If the backend is unreachable and this is a new tool, return a clear stub message
        if (NEW_TOOL_NAMES.has(toolName)) {
          send({
            jsonrpc: '2.0',
            id,
            result: {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify({
                    status: 'not_implemented',
                    tool: toolName,
                    message: `The '${toolName}' tool is defined in the MCP layer but the backend handler is not yet deployed. Backend error: ${err.message}`,
                  }, null, 2),
                },
              ],
              isError: false,
            },
          });
        } else {
          send({ jsonrpc: '2.0', id, error: { code: -32000, message: err.message } });
        }
      }
    }
  • The callBackend helper function that makes HTTP POST requests to the backend MCP endpoint with Bearer token auth.
    function callBackend(body) {
      return new Promise((resolve, reject) => {
        const payload = JSON.stringify(body);
        const isHttps = parsedBase.protocol === 'https:';
        const lib = isHttps ? https : require('http');
        const options = {
          hostname: parsedBase.hostname,
          port: parsedBase.port || (isHttps ? 443 : 80),
          path: MCP_PATH,
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
            'Authorization': `Bearer ${API_KEY}`,
            'Content-Length': Buffer.byteLength(payload),
          },
        };
    
        const req = lib.request(options, (res) => {
          let data = '';
          res.on('data', chunk => data += chunk);
          res.on('end', () => {
            try {
              resolve(JSON.parse(data));
            } catch (e) {
              reject(new Error(`Invalid JSON from backend: ${data.slice(0, 200)}`));
            }
          });
        });
    
        req.on('error', reject);
        req.write(payload);
        req.end();
      });
    }
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 only states 'Search for job listings' without disclosing behavior like pagination, default limit, or whether results are from external sources. Minimal transparency.

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 a single concise sentence with no wasted words. Could be slightly more informative without being verbose.

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 output schema and no annotations, the description is insufficient. It lacks details on what the search returns, default limit, or any response format. Completeness is low for a search tool.

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?

Input schema has 100% description coverage for all six parameters. The description adds no extra meaning beyond the schema, so baseline score of 3 applies.

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 resource 'job listings' with optional filters. It is distinguishable from siblings like 'get_recommended_jobs' and 'match_job', but does not explicitly highlight differences.

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 on when to use this tool vs alternatives such as 'get_recommended_jobs' or 'match_job'. No exclusions or context provided.

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/Exidian-Tech/placed-mcp'

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