Skip to main content
Glama

Remotejobify

Search remote jobs

search_jobs
Read-onlyIdempotent

Search open remote jobs on Remotejobify by where the person lives. Each job comes with who can apply, the line from the listing that proves it, pay when listed, and a link. Pass country whenever you know where they live: most remote jobs are only open to some countries. Without it you get jobs open worldwide.

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
roleNoA job type, to narrow the search. Optional.
limitNoHow many jobs, up to 20. 10 if not given.
queryNoWords for the job title or company, like "customer support", "python" or "nurse". Optional.
countryNoThe country the person lives in: a name ("Philippines", "UK") or a two-letter code ("PH", "GB").
working_hoursNodaytime: the job keeps business hours that are daytime where they live. night_shift: night there (only jobs whose listing states its hours). part_time: part-time jobs. daytime and night_shift need country.

Output Schema

NameRequiredDescriptionDefault
jobsYes
moreYes
totalYes
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely useful context beyond them: the country-scoping rule and what happens when country is omitted, which affects result interpretation. It says little about result volume or pagination, but the output schema covers return shape.

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?

Front-loaded with purpose, then the highest-value guidance about country. Slightly padded by the enumeration of job fields (who can apply, proof line, pay, link), which partly overlaps what the output schema already provides.

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?

An output schema exists, so return values need no prose, and the description correctly focuses on the one parameter choice that most changes results. With zero required parameters and full schema coverage, this is close to complete for a search 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 100%, so baseline is 3, but the description adds real meaning: it justifies the country parameter ('most remote jobs are only open to some countries') and explains the behavioral consequence of omitting it. The working_hours/country dependency is left to the schema's own enum descriptions.

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?

States a specific verb and resource ('Search open remote jobs on Remotejobify') and adds a distinguishing scope: 'by where the person lives'. That scope separates it from a generic search/fetch sibling, though no sibling is named explicitly.

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?

'Pass country whenever you know where they live' plus 'Without it you get jobs open worldwide' gives clear conditional usage and states the fallback outcome. It does not say when to prefer this over get_job or fetch, so it stops short of explicit alternatives.

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