Skip to main content
Glama

Remotejobb

List companies

list_companies
Read-onlyIdempotent

Lists companies on Remotejobb.se with their number of open jobs, website and company page, with paging. Without a name, companies with the most open jobs come first. With a name, companies are matched loosely (case, accents, punctuation and legal suffixes such as "AB" are ignored; every word must start a word of the company name) and the closest matches come first. The slug can be used as the company filter of search_jobs.

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": "list_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name to look for, e.g. "spotify" or "academic work".
pageNoPage number.
limitNoCompanies per page.
languageNoLanguage for labels such as work mode and employment type. Job content is returned in its original language.en
is_hiringNotrue: only companies with open jobs. false: also companies without open jobs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already mark this as a read-only, idempotent, non-destructive, closed-world operation, and the description adds substantial behavior beyond that: it lists returned fields, explains paging, describes ordering with and without a name, and specifies loose matching rules. It also explains how the slug can be reused in search_jobs, which is useful cross-tool 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?

The description is compact and front-loaded: it first states what the tool lists and returns, then covers paging and ordering, then matching behavior, then the cross-tool slug use. Every sentence carries information needed to call or interpret the tool, with no redundant restatement of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given five optional parameters, full schema descriptions, annotations, and no output schema, the description is complete enough for an agent to call it correctly. It covers the returned fields, paging, ordering, name-matching semantics, and the practical link to search_jobs without needing an output schema.

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 the schema already documents each parameter and its defaults. The description still adds meaningful semantics for the name parameter by explaining case/accent/punctuation/legal-suffix normalization and the requirement that every word start a word of the company name, and it explains ordering effects tied to the presence of a name; it does not add much beyond the schema for language or is_hiring.

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?

The description states a specific verb and resource: it lists companies on Remotejobb.se and names the returned fields (open job count, website, company page), paging, and ordering behavior. The mention of the slug as a company filter for search_jobs helps distinguish this company-listing tool from the job-search sibling.

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?

It gives clear conditional guidance for using the name parameter: without a name, results are ordered by open-job count; with a name, loose matching and closest-match ordering apply. It also links the returned slug to search_jobs, but it does not explicitly state when to use this tool instead of search_jobs or get_job in broader terms, and it gives no exclusion conditions.

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.