Skip to main content
Glama

Remotejobb

Search jobs

search_jobs
Read-onlyIdempotent

Searches open remote and hybrid jobs listed on Remotejobb.se, a Swedish job board. All filters are optional and combine with AND; a filter given several values matches jobs with any of them. Returns compact job summaries with paging, the applied order, and facets: the number of matching jobs per filter value, each counted with the other filters applied. Full descriptions and apply links are returned by get_job.

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
cityNoCity of hybrid jobs, as a name or slug, e.g. "Göteborg", "Gothenburg" or "goteborg". Accepts one value or a list; a list matches any of its values.
pageNoPage number.
orderNoSort order. "relevance": best keyword match first (the default with a query). "published_at": newest first (the default without a query). "apply_by": earliest application deadline first, jobs without a deadline last. "salary": highest stated salary first, jobs without a salary last.
queryNoKeywords matched against job title, company name and description, e.g. "laravel developer". Every word must match, as a prefix.
companyNoCompany name or slug. Names match loosely: case, accents, punctuation and legal suffixes such as "AB" are ignored, and every word must start a word of the company name, so "spotify" matches "Spotify AB". Accepts one value or a list; a list matches any of its values.
categoryNoJob category, as a slug or name. list_search_filters lists the categories. Accepts one value or a list; a list matches any of its values.
languageNoLanguage for labels such as work mode and employment type. Job content is returned in its original language.en
per_pageNoResults per page.
work_modeNo"remote" for fully remote jobs, "hybrid" for jobs that are partly on site. Accepts one value or a list; a list matches any of its values.
ad_languageNoLanguage the job ad is written in: "sv" (Swedish) or "en" (English). Accepts one value or a list; a list matches any of its values.
salary_onlyNoOnly jobs that state a salary.
remote_scopeNoWhere applicants may live. Matches this scope and anything more open, e.g. "eu" also returns "europe" and "worldwide" jobs.
employment_typeNoType of employment. Accepts one value or a list; a list matches any of its values.
posted_within_daysNoOnly jobs published within this many days.
min_monthly_salary_sekNoMinimum monthly salary in SEK. Yearly and hourly salaries are converted. Only matches jobs that state a salary in SEK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that: results are compact summaries, paging is applied, the effective sort order is reported, and facet counts are computed with the other filters applied — a nuance that materially affects how an agent should read the response. No auth, rate-limit, or result-cap information is given.

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?

Three sentences, front-loaded with purpose and scope, then filter-combination semantics, then return shape and the sibling handoff. Every sentence carries distinct information and nothing is repeated from the schema.

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 15 parameters, no required fields and no output schema, the description carries the burden of describing returns — and it does, covering summaries, paging, applied order and facets. Remaining gaps (defaults, result caps, empty-result behavior) are handled by the schema, so the definition is close to complete for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so per-parameter meaning is already documented and the baseline would be 3. The description earns above baseline by stating the cross-parameter rule the schema never states globally: filters are all optional and combine with AND, while multiple values within one filter match any of them.

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 and resource ("Searches open remote and hybrid jobs") plus the source domain (Remotejobb.se, a Swedish job board), which sets scope immediately. It also draws the boundary with the sibling get_job, so an agent knows this tool returns summaries while get_job returns full descriptions and apply links.

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?

Explains that all filters are optional and how they combine (AND across filters, OR within a multi-value filter), which is the key guidance for constructing a query. It routes full-detail needs to get_job, but does not state when this tool is the wrong choice or how it relates to list_search_filters/list_companies beyond a passing mention in the schema.

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.