Skip to main content
Glama

RemoteHunt

Search remote jobs

search_remote_jobs
Read-onlyIdempotent

Find open remote jobs on RemoteHunt for a job title or profession. With the country the person lives in, only jobs whose postings say they can hire there are returned. Returns up to 10 jobs with title, company, posting age, stated pay, where each job can hire, and a link to its RemoteHunt page.

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": {
      "role": "<role>"
    },
    "name": "search_remote_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesJob title or profession, e.g. "product designer" or "data analyst".
levelNoOptional level: junior, mid, senior or lead.
limitNoHow many jobs to return, 1 to 10.
countryNoCountry the person lives in: a name or an ISO code, e.g. "Brazil" or "BR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavior, so the description only needs to add context. It contributes the result cap ("up to 10 jobs"), the semantics of the country filter against posting text, and an enumeration of returned fields, though it says nothing about empty-result behavior or ranking.

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 with no filler: purpose first, the country filter's effect second, and the return shape last. Each sentence carries distinct information an agent would otherwise have to infer.

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?

For a four-parameter read-only search with no output schema, the description covers purpose, filter behavior, and returned fields well enough to call it correctly. Minor gaps remain around result ordering and what happens when nothing matches.

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 100% and every parameter is already documented, so the baseline is 3. The description adds a little meaning for country (results are limited to postings that state they can hire there), but role, level, and limit are left entirely to the schema.

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?

"Find open remote jobs on RemoteHunt for a job title or profession" gives a specific verb, resource, and scope, and the second sentence narrows what results mean. It does not explicitly contrast with the get_job or can_job_hire_me siblings, so it stops short of 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 implied through the role-based search and the explanation of what passing a country does, but there is no explicit "use this when..." framing or exclusion pointing to get_job for a single posting or can_job_hire_me for eligibility checks.

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