Skip to main content
Glama
Sign In

Remotejobb

by se.remotejobb
OverviewDiscussionsAdmin

Get job details

get_job
Read-onlyIdempotent

Gets up to 5 jobs from Remotejobb.se by id: the full description (when the source allows it), salary, employment details, apply link and application deadline (apply_by). apply_method is "email" when applications are sent by email; apply_url then links to the job page on Remotejobb.se instead of opening an email app. Ids that are not available are listed in not_found. With with_similar, each job also lists up to 5 other open jobs in the same category. Ids come from search_jobs.

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": {
      "ids": "<ids>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesJob ids, as returned by search_jobs (1 to 5). With more than one job, each description is shortened to 3000 characters.
languageNoLanguage for labels such as work mode and employment type. Job content is returned in its original language.en
with_similarNoAlso return up to 5 other open jobs in the same category for each job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral details: incomplete source descriptions, truncation behavior implied by the schema, not_found ids, and the special apply_method/apply_url behavior for email applications. These are meaningful operational details an agent needs when interpreting results.

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?

The description is dense but front-loaded, starting with the core operation and then covering edge cases. Most sentences earn their place, though the single paragraph packs many conditional details together.

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?

There is no output schema, so the description carries the full burden of explaining return content. It covers the main returned fields, not_found handling, apply link semantics, truncation-related caveats, and optional similar jobs, making it complete for this tool.

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 already 100%, so the schema documents all three parameters. The description still adds useful meaning by tying ids to search_jobs and explaining that with_similar returns up to 5 other open jobs in the same category for each job.

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: getting up to 5 jobs by id from Remotejobb.se. It clearly lists the returned information and distinguishes this lookup from the search-oriented sibling by noting that ids come from search_jobs.

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 usage context by saying ids come from search_jobs and explains the effect of with_similar. It does not explicitly state when not to use it, but the id-based lookup versus search distinction is implicit and strong.

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

All Remotejobb 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