Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_apac_jobs

Read-onlyIdempotent

Search active APAC job listings across JobStreet, JobsDB, and SEEK to find hiring companies, disclosed salary bands, and role matches by country, location, work arrangement, and posting date.

Instructions

Search active APAC job listings, hiring companies, and disclosed salary bands across JobStreet, JobsDB, and SEEK covering Singapore (SG), Malaysia (MY), Philippines (PH), Indonesia (ID), Hong Kong (HK), Thailand (TH), Australia (AU), and New Zealand (NZ) (corridordata/jobstreet-jobsdb-apac-scraper).

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_apac_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsNoSearch query for role, skill, or employer name.software engineer
locationNoOptional city or sub-region filter (e.g. 'Kuala Lumpur', 'Makati', 'Central').
maxItemsNoMaximum APAC job listings to return.
countriesNoAPAC market portals to query in parallel.
withSalaryOnlyNoOnly return listings with publicly stated salary bands.
workArrangementNoOptional Remote / Hybrid / On-site filter.all
postedWithinDaysNoOnly include listings posted within the last N days.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that data comes from the named Apify actor (`corridordata/jobstreet-jobsdb-apac-scraper`) and that listings are 'active', which is useful provenance. It adds nothing about billing/PPE charges, result latency, or what happens when a portal returns nothing — relevant given the maxTotalChargeUsd parameter.

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?

A single front-loaded sentence covering verb, resource, sources, and coverage, with no filler. The trailing actor-slug parenthetical is the only element that reads as boilerplate rather than agent-relevant guidance.

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 no output schema, the description usefully names the return content (listings, hiring companies, salary bands), and it enumerates the supported markets that the enum alone would convey less readably. Given annotations already cover safety and the schema is fully documented, the main remaining gap is behavioral detail around cost and result volume, not core call correctness.

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 the schema already documents all eight parameters including defaults and enums. The description only reinforces meaning indirectly — the country list and 'disclosed salary bands' map to `countries` and `withSalaryOnly` — without adding syntax, format examples, or interaction rules 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?

Specific verb+resource: 'Search active APAC job listings' plus the three portals (JobStreet, JobsDB, SEEK) and the eight covered markets, so an agent knows exactly what corpus is queried. It does not name or contrast against a sibling such as search_multi_ats_jobs, so the differentiation burden falls to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description defines scope (APAC portals, active listings, disclosed salary bands) but never states when to choose this tool over the ATS/other job-search siblings, nor any prerequisitives or exclusions. All routing information must be inferred from the geographic scope alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.