Skip to main content
Glama

searchnapply

This connector has been deprecated

Replaced by searchnapply.

Deprecated.

Search job postings

job_postings_search
Read-onlyIdempotent

Purpose: Find job postings that fit the user's role, location and fields, with a short summary per posting. When: The user describes work they want; gather role and location first; in a chat app show results with job_postings_search_widget_render, unasked, and in a terminal as text. Cost: About 170 tokens per posting and 3020 for 20 postings.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pageSize": 20,
      "locations": [
        "Austin, TX"
      ],
      "titleText": "QA engineer",
      "department": "software-it",
      "experience": {
        "min": "Mid level"
      }
    },
    "name": "job_postings_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe 1-based page number.
sortByNoResult order; job_postings_search_fields explains each value.
keywordsNoWords that must appear in the posting's text.
pageSizeNoPostings per page, 1 to 50.
companiesNoCompany names; a posting from any of them is kept.
locationsNoLocation names in plain words, each read as the closest known location, so check resolvedLocations for what was actually searched.
salaryMaxNoHighest yearly salary to keep, in US dollars after the same conversion.
salaryMinNoLowest yearly salary to keep, in US dollars after each posting's published salary is converted.
titleTextNoWords of the job title, matched to one of searchnapply's known roles (resolvedRole.display names it), else matched against posting titles.
datePostedNoHow recently the posting was published; leave it out for any date.
departmentNoOne department slug, to narrow a title that spans departments; call job_postings_search_fields for what each one holds.
experienceNoExperience level to keep, as exactly one of exact or min.
includeFamilyNoAlso return postings from the resolved role's wider family; false, the default, keeps the exact role only.
locationTypesNoWorkplace types to keep.
employmentTypeNoEmployment type to keep.
excludeKeywordsNoWords that must not appear in the title or the text, 1 to 10 words.
includeNoSalaryNoKeep postings that publish no salary; true by default.

Output Schema

NameRequiredDescriptionDefault
hintNoWhat to do next when the result needs a decision or a retry.
pageYesThe 1-based page returned.
facetsNoHow the matches split by department; absent on a narrowed or empty search.
pageSizeYesHow many postings a page holds.
postingsYesThe matching postings, one summary each.
titleNoteNoPresent when no role matched: the title words were matched against posting titles.
totalCountYesHow many postings match in total.
totalPagesYesHow many pages the matches fill.
familyLabelNoThe name of the role's wider family.
familyTotalNoHow many more postings the role's wider family holds; present when the exact result is short.
resolvedRoleNoThe role the title words were read as; absent when no role matched.
resolvedLocationsNoThe locations that were searched, as resolved from the location names given.
totalCountIsCappedYesTrue when the count stopped at 1,000 and more postings match.
unrecognizedLocationsNoThe location names that matched no known location and were left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / titleText / description
      Previous value: -"Words of the job title, matched to one of searchnapply's known roles when one fits (resolvedRole.display names it) and otherwise matched against posting titles."New value: +"Words of the job title, matched to one of searchnapply's known roles (resolvedRole.display names it), else matched against posting titles."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is settled. The description adds something annotations cannot: an explicit cost estimate (~170 tokens per posting, ~3020 for 20), letting an agent size pageSize sensibly. It adds no detail on empty results or location-resolution surprises beyond what the schema says.

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?

Three labeled sentences (Purpose/When/Cost) that are front-loaded and free of filler; each sentence earns its place. The labeling is mildly mechanical but makes scanning fast for an agent.

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?

A 17-parameter tool with an output schema and fully documented parameters needs relatively little prose, and the description covers trigger, ordering, sibling hand-off, and cost. The remaining gap is guidance on combining many optional filters or handling zero-result searches, which an agent must infer.

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% and the schema already explains page/pageSize, salary conversion, location resolution, and the experience min/exact split. The description only echoes that role and location are the key filters, adding no syntax or precedence guidance beyond the structured fields. 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?

States a specific verb and resource (find job postings) plus the scope (role, location, fields) and the return shape (short summary per posting). It also names the widget-render sibling as the display step, which helps separate searching from rendering, though it never clarifies its relationship to job_postings_get_full_description.

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

Usage Guidelines4/5

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

The 'When' clause gives a concrete trigger (the user describes work they want), a prerequisite (gather role and location first), and a post-call routing rule (render via job_postings_search_widget_render unasked in chat, plain text in a terminal). It does not state when not to use this tool, e.g. when a full description is wanted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources