Skip to main content
Glama

search_jobs_multi

Read-onlyIdempotent

Search multiple job boards simultaneously by keyword, location, and posting age to gather matching job listings from LinkedIn, Indeed, Glassdoor, and ZipRecruiter.

Instructions

Search multiple public job boards (LinkedIn, Indeed, Glassdoor, ZipRecruiter) simultaneously.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kw": "<kw>"
    },
    "name": "search_jobs_multi"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwYesJob title or skill keyword to search across job boards
ageNoMaximum posting age in hours (default 168 = 7 days)
locNoGeographic location or 'Remote'
limitNoMaximum results to return per job board (default 5)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.8
    • addedInput schema / properties / age / description
      Added value: +"Maximum posting age in hours (default 168 = 7 days)"
    • addedInput schema / properties / kw / description
      Added value: +"Job title or skill keyword to search across job boards"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum results to return per job board (default 5)"
    • addedInput schema / properties / loc / description
      Added value: +"Geographic location or 'Remote'"
  2. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that results come from external third-party boards (LinkedIn, Indeed, Glassdoor, ZipRecruiter), but says nothing about whether results are merged or deduplicated, whether boards can fail independently, or any rate/availability constraints.

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?

One short sentence with a front-loaded verb and no filler; the board list is the only embellishment and it does inform scope. Its brevity is also the source of the missing routing guidance, but nothing is redundant.

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?

With four fully documented parameters, an output schema, and complete annotations, most needs are met by structured fields. The remaining gap is behavioral detail specific to a multi-source search — notably whether the per-board limit yields an aggregated or per-board result set — which the description leaves unstated.

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%, with kw, age, loc, and limit each documented including defaults and units (hours, per-board cap). The description adds no meaning beyond that, so the baseline 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 gives a specific verb ('Search') and resource ('multiple public job boards') and enumerates the four boards covered, which implicitly sets it apart from single-source siblings like search_jobs. However, it never explicitly contrasts itself with search_jobs or search_jobs_advanced, so an agent must infer the difference from the name alone.

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?

Usage is only implied: 'simultaneously' across multiple boards suggests this is the broad-coverage choice, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent facing search_jobs, search_jobs_advanced, and smart_match_jobs gets no routing instruction here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.