Skip to main content
Glama

Search remote jobs at foreign companies

search_remote_jobs
Read-onlyIdempotent

Remote roles at foreign companies (techjobs.vn /remote), by default only those someone living in Vietnam can take. For companies hiring in Vietnam use 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": "search_remote_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of `limit` results, starting at 1; up to page 3 without sign-in.
roleNoPart of the role name, e.g. "Backend" or "Product Manager".
limitNoMaximum jobs to return (default 10): up to 10 without sign-in, 50 when signed in.
queryNoWords in title, company or location, e.g. "backend" or "apac".
open_to_vietnamNoDefault true: only roles someone in Vietnam can take. false adds country-restricted ones.

Output Schema

NameRequiredDescriptionDefault
jobsYes
totalYes
noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, so the safety profile is covered. The description adds genuine context beyond that: the upstream source and the non-obvious default filter that silently excludes country-restricted postings unless open_to_vietnam is false. It does not mention auth or the unauthenticated result caps, but the schema parameters already state those.

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?

Two short sentences, zero filler. The behavioral scope is front-loaded and the disambiguation to search_jobs comes second, which is the right order for an agent deciding whether to call this at all.

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 an output schema present and rich annotations, the description does not need to explain return values, and it correctly focuses on scope and routing. The only small gap is that it never states how results relate to search_jobs (overlap or exclusivity), which an agent picking between the two might wonder about.

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 100%, so page, limit, query, role and open_to_vietnam are all documented in the schema. The description's scope sentence about Vietnam-eligibility merely echoes what open_to_vietnam already explains, adding no new syntax or format guidance. Baseline 3 applies when the schema carries the semantics.

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?

States a specific verb+resource (remote roles at foreign companies) and pins the exact source (techjobs.vn /remote). It also clarifies the default scope constraint (only those someone living in Vietnam can take), which distinguishes it from the sibling search_jobs without opening either schema.

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?

Explicitly routes the agent: 'For companies hiring in Vietnam use search_jobs.' That names the primary alternative and the condition that selects it. It stops short of covering other nearby siblings such as suggest_jobs_for_me or search_companies, so it is clear but not exhaustive.

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