Skip to main content
Glama

Remote Nomad Jobs

Search work-from-anywhere jobs

search_jobs
Read-onlyIdempotent

Search open remote jobs that can be done from anywhere in the world. All filters are optional; with no filters it returns the newest jobs. Results are sorted newest first and include salary when the employer published one.

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
pageNoPage of results, 20 per page. Only for a connected member account (see more_results.next_page); otherwise the preview is returned.
perkNoSpecial filter, e.g. 'no-phone' or 'hiring-immediately'.
queryNoKeywords matched against job title, company, category, and tags, e.g. 'customer support' or 'react'.
companyNoExact company name, e.g. 'GitLab'.
categoryNoJob category. See list_filters for the full list.
entry_levelNoOnly jobs open to people without prior experience.
min_salary_usdNoMinimum yearly salary in USD. Only jobs that publish a salary can match.
employment_typeNo

Output Schema

NameRequiredDescriptionDefault
jobsYes
accessYesfull when a connected member account sees every match.
more_resultsYes
total_matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page of results, 20 per page. Only for a connected member account (see more_results.next_page); otherwise the preview is returned.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / access
      Added value: +{
      +  "description": "full when a connected member account sees every match.",
      +  "enum": [
      +    "preview",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / more_results / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "all_results_url": {
      -        "type": "string"
      -      },
      -      "not_shown": {
      -        "type": "number"
      -      },
      -      "note": {
      -        "type": "string"
      -      },
      -      "plans_url": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "not_shown",
      -      "note",
      -      "all_results_url"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "all_results_url": {
      +        "type": "string"
      +      },
      +      "next_page": {
      +        "type": "number"
      +      },
      +      "not_shown": {
      +        "type": "number"
      +      },
      +      "note": {
      +        "type": "string"
      +      },
      +      "plans_url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "not_shown",
      +      "note",
      +      "all_results_url"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "total_matches",
      -  "jobs",
      -  "more_results"
      -]New value: +[
      +  "total_matches",
      +  "access",
      +  "jobs",
      +  "more_results"
      +]
  2. Changed3 schema fields changed
    • removedOutput schema / properties / jobs / items / properties / featured
      Removed value: -{
      -  "description": "A paid featured listing. Featured jobs are shown first, as on the website.",
      -  "type": "boolean"
      -}
    • changedOutput schema / properties / jobs / items / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "company",
      -  "salary",
      -  "employment_type",
      -  "category",
      -  "posted_date",
      -  "url",
      -  "company_url",
      -  "featured"
      -]New value: +[
      +  "id",
      +  "title",
      +  "company",
      +  "salary",
      +  "employment_type",
      +  "category",
      +  "posted_date",
      +  "url",
      +  "company_url"
      +]
    • changedOutput schema / properties / more_results / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "all_results_url": {
      -        "type": "string"
      -      },
      -      "not_shown": {
      -        "type": "number"
      -      },
      -      "note": {
      -        "type": "string"
      -      },
      -      "plans_url": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "not_shown",
      -      "note",
      -      "all_results_url",
      -      "plans_url"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "all_results_url": {
      +        "type": "string"
      +      },
      +      "not_shown": {
      +        "type": "number"
      +      },
      +      "note": {
      +        "type": "string"
      +      },
      +      "plans_url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "not_shown",
      +      "note",
      +      "all_results_url"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. 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 readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds value beyond that by disclosing sort order (newest first) and that salary appears only when published, which an agent could not infer from annotations. It does not itself mention the preview-vs-paginated result limitation, though the schema documents it.

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 short sentences, front-loaded with the core purpose, followed by default behavior and result ordering. Every sentence carries information and nothing is padded.

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 8 optional params at 88% coverage, rich annotations, and an output schema covering return values, the description supplies the remaining context an agent needs: default unfiltered behavior, sort order, and salary presence. It stops short of explaining pagination/preview semantics, but that is delegated to the schema.

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 description coverage is 88%, so the parameters are already well documented, including the min_salary_usd caveat that only salary-publishing jobs can match. The description adds only the general note that filters are optional and the default behavior without filters, which is marginal beyond 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?

The description names a specific verb and resource (search open remote jobs) and narrows the scope to work-from-anywhere roles, which distinguishes it from a generic job lookup like get_job. It does not explicitly contrast itself with siblings such as search_companies, but the resource is unambiguous.

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?

It states that all filters are optional and that an unfiltered call returns the newest jobs, which is useful invocation guidance. It gives no when-not guidance, no pointer to list_filters for valid category/perk values, and no routing toward get_job for a single posting, so usage is only implied for edge cases.

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