Skip to main content
Glama

search_jobs

Search live job listings across multiple free job boards by title, skills, or keywords, with options to filter remote roles and limit results.

Instructions

Search for latest job listings from multiple free job boards (Remotive, Arbeitnow)

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": {
      "query": "<query>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (max 20)
queryYesJob title, skills, or keywords e.g. 'React developer' or 'data analyst'
remoteOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. It usefully reveals the upstream providers (Remotive, Arbeitnow) and that they are free boards, implying no auth is needed, but says nothing about rate limits, result freshness, deduplication across boards, or network failure behavior.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the resource, the scope, and the source list are all packed into one line.

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?

There is no output schema and no annotations, so the definition must convey what a result looks like (fields such as title, company, location, URL) and how results are ordered or truncated. It provides none of that, and leaves remoteOnly undocumented, which is thin for a three-parameter 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?

Schema coverage is 67%: query and limit are documented in the schema, while remoteOnly has no description anywhere. The description adds no new meaning about how query terms map to providers or how remoteOnly interacts with boards that are inherently remote, so it merely matches the schema baseline.

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 and resource ('Search for latest job listings') plus the data sources ('Remotive, Arbeitnow'), which is enough to separate it from the resume/application-oriented siblings. It stops short of explicitly contrasting itself with any named alternative, so it is clear but not maximally distinguishing.

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?

The phrase 'latest job listings' and the naming of external free job boards imply a discovery use case, but nothing states when to prefer this over the match-analysis or application-tracking siblings, or whether results are fresh versus cached. Usage is only inferable.

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