Skip to main content
Glama

Locate Jobs Network Job Search

by com.locatejobsnetwork
OverviewDiscussionsAdmin

Search jobs

search_jobs
Read-only

Search live jobs on the 20 Locate Jobs Network job boards: Diversity Careers, Healthcare Jobs for Veterans, Nature Jobs, University Fundraising Jobs, Fiber Optic Jobs, Certified Medical Assistant Jobs, Forklift Jobs, HR Analyst Jobs, The Trades Jobs, IT Jobs, Optometry Jobs, Dentist Jobs, Funeral Service Jobs, Chiropractor Jobs, Veterinarian Jobs, SLP Jobs, Diversity Higher Education Jobs, Minority Finance Jobs, Bioinformatics Jobs, and Minority Jobs. Search by role or skill, by place (a city and state, a state, or a ZIP code, which searches its whole state), or for remote jobs. Returns 5 to 10 current jobs with title, employer, location, posted date, and a link to the job page on the board that lists it, plus a link to see more. It only reads job listings: it cannot apply for a job, post a job, or save a search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whatNoThe role or skill, such as "dental hygienist", "forklift", or "payroll". Every word must appear in the job title or the employer's name, so keep it to the words a title uses ("help desk", not "IT help desk support role"). Leave out to list the newest jobs.
limitNoHow many jobs to return, 5 to 10. Defaults to 10.
whereNoA city with its state ("Columbus, OH"), a state, a ZIP code (searches its whole state), or "remote". Leave out for the whole U.S.
remoteNotrue for remote jobs only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobsYes
searchedYes
seeMoreUrlYesOur search page with more jobs like these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / what / description
      Previous value: -"The role or skill, such as \"payroll\", \"help desk\", or \"HR analyst\". Leave out to list the newest desk jobs."New value: +"The role or skill, such as \"dental hygienist\", \"forklift\", or \"payroll\". Every word must appear in the job title or the employer's name, so keep it to the words a title uses (\"help desk\", not \"IT help desk support role\"). Leave out to list the newest jobs."
    • changedInput schema / properties / where / description
      Previous value: -"A city with its state (\"Columbus, OH\"), a state, a ZIP code, or \"remote\". Leave out for the whole U.S."New value: +"A city with its state (\"Columbus, OH\"), a state, a ZIP code (searches its whole state), or \"remote\". Leave out for the whole U.S."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/not destructive/closed-world, but the description goes further by stating it cannot apply for a job, post a job, or save a search, and by scoping results to 5-10 current listings. It adds useful boundaries on top of the safety hints, though it says nothing about rate limits, auth, or result freshness mechanics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and well structured, but the enumeration of all 20 board names consumes a large share of the text and adds little decision value versus saying 'the 20 Locate Jobs Network boards'. The board list is scope-relevant yet disproportionate to the rest.

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 4-optional-param search tool with an output schema and full annotation coverage, the description supplies purpose, usage modes, and negative capabilities. Return-value detail is present and, because an output schema exists, that redundancy is harmless rather than required.

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 each parameter already carries thorough guidance (word-matching rules for 'what', accepted formats for 'where', default of 10 for 'limit'). The description only restates the same search dimensions, adding no new semantics, so the baseline 3 applies.

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?

States a specific verb (search) and resource (live jobs across the 20 named boards), plus the search modalities and return shape. An agent immediately knows this is a job-listing lookup over a fixed network, not a general web search. No siblings exist, so there is nothing to disambiguate against.

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?

Enumerates the valid usage modes: by role or skill, by place (city+state, state, or ZIP which searches its whole state), or for remote jobs. This is clear context for how to invoke it, but no when-not guidance or exclusions beyond the negative-capability sentence.

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

All Locate Jobs Network Job Search toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources