Skip to main content
Glama

Search tech jobs in Vietnam

search_jobs
Read-onlyIdempotent

Search open tech jobs at companies hiring in Vietnam, refreshed hourly by techjobs.vn. Use when the user looks for jobs by role, skill, seniority, city or company. Returns the best matches, newest first, each with a techjobs.vn link to share with the user.

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
cityNohcm = Ho Chi Minh City, hanoi = Hà Nội; remote covers remote-vn and remote-global.
pageNoPage of `limit` results, starting at 1; up to page 3 without sign-in.
limitNoMaximum jobs to return (default 10): up to 10 without sign-in, 50 when signed in.
queryNoFree-text words matched against job title, company and skills, e.g. "react frontend". Title matches rank first.
skillsNoEvery listed skill must be required by the job, e.g. ["react", "typescript"].
companyNoCompany slug or exact name, e.g. "grab" or "OPSWAT".
seniorityNoSeniority levels, any of: intern, junior, mid, senior, lead.
response_formatNoconcise (default) returns title, company and link; detailed adds cities, seniority, work mode, stated pay and skills.
posted_within_daysNoOnly jobs first posted within this many days.

Output Schema

NameRequiredDescriptionDefault
jobsYes
totalYes
noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / response_format / description
      Previous value: -"concise (default) returns title, company and link; detailed adds city, seniority and skills."New value: +"concise (default) returns title, company and link; detailed adds cities, seniority, work mode, stated pay and skills."
    • addedOutput schema / properties / jobs / items / properties / cities
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / jobs / items / properties / salary
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "currency": {
      +          "type": "string"
      +        },
      +        "max": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "min": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "period": {
      +          "anyOf": [
      +            {
      +              "enum": [
      +                "month",
      +                "year",
      +                "hour"
      +              ],
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        }
      +      },
      +      "required": [
      +        "min",
      +        "max",
      +        "currency",
      +        "period"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Pay stated in the JD (gross/net often unsaid); null when not stated."
      +}
    • addedOutput schema / properties / jobs / items / properties / workplace_type
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, read-only lookup, so the bar is lower. The description still adds real behavior beyond them: results are refreshed hourly, ranked by best match with newest first, and each carries a shareable techjobs.vn link — the ranking order and shareability are not derivable from the annotations.

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 tight sentences: what it is, when to use it, what comes back. Purpose and trigger are front-loaded and no sentence is filler.

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 nine all-optional parameters, full schema documentation, an output schema and complete annotations, the description covers the essentials an agent needs to call it. The one gap is that the anonymous-vs-signed-in limits (page 3 / 10 vs 50 results) live only in the schema and are not surfaced as behavioral context.

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%, including enum explanations, so the schema carries the parameter burden and a 3 baseline applies. The description only restates the filter facets generically ('by role, skill, seniority, city or company') without adding syntax or matching semantics beyond what each property already documents.

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 tech jobs at companies hiring in Vietnam') plus the data source and refresh cadence. Scope facets (role, skill, seniority, city, company) reinforce it, but the description never distinguishes it from overlapping siblings such as search_remote_jobs or suggest_jobs_for_me.

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?

'Use when the user looks for jobs by role, skill, seniority, city or company' gives a clear trigger condition tied to concrete user intents. It offers no exclusions or named alternatives, so an agent must infer on its own when search_remote_jobs or suggest_jobs_for_me would be a better pick.

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