Skip to main content
Glama

OfferMagnet Jobs

Search jobs

search_jobs
Read-onlyIdempotent

Search live job postings by keywords, country, contract type, remote, visa sponsorship, employer and age. Returns title, company, location, salary when posted, visa reading with the quoted sentence, the employer's apply link and an OfferMagnet link that tailors a resume and applies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeywords: job title, skill or company, e.g. "machine learning engineer".
typeNoContract type.
visaNoyes = the posting offers visa sponsorship; no = it refuses it or requires citizenship.
limitNoResults per page (default 20).
offsetNoPagination offset.
remoteNotrue = remote postings only, false = on-site/hybrid only.
companyNoExact employer name, e.g. "Anthropic".
countryNoISO 3166 alpha-2 country, e.g. US, FR, GB, ES, DE, CA.
posted_daysNoOnly postings from the last N days (default 45).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it discloses what the results contain, including the visa reading with its quoted sentence and the employer apply link, which tells the agent what evidence it will get back. It omits pagination behavior, which is only in the schema.

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?

Two sentences, front-loaded with the action and filters, then the return payload. Dense but every clause carries information; the long return enumeration is slightly list-like but justified since no output schema exists.

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 nine optional parameters, no required fields, and no output schema, the description needs to convey both filtering scope and return shape, and it does both. The only gap is pagination and result-count behavior, which the schema covers for limit/offset but the description never ties together.

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 enums and examples already documenting every parameter, so the schema does the heavy lifting. The description's filter list mirrors the schema without adding syntax, defaults, or interaction rules (e.g. how q combines with company), 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 opens with a specific verb and resource ('Search live job postings') and enumerates the filterable dimensions (keywords, country, contract type, remote, visa, employer, age), so the tool's function is unambiguous. It does not explicitly contrast itself with siblings like get_job or job_market_stats, which keeps it from a 5.

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: the word 'Search' plus the filter list suggests this is the discovery entry point, but there is no explicit when-to-use guidance, no mention of when to prefer get_job for a single posting, and no stated prerequisites. An agent can infer the role but must reason about alternatives itself.

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