Skip to main content
Glama

Loker Dollar Jobs

search_jobs

Search active remote / Indonesia-friendly jobs. Returns basic job fields + an apply URL. On the free tier, results may include promoted listings labeled sponsored: true.

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
qNoFree-text query (title, company, skills).
limitNo1–50 (default 20).
localeNoid | en (default id).
offsetNoResult offset for pagination.
job_typeNofull-time | part-time | contract | freelance
locationNoLocation text filter.
remote_typeNoworldwide | regional | timezone-based
opportunity_typeNoregular | internship | fellowship | apprenticeship | volunteer | gig (default: regular)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedInput schema / properties / category
      Removed value: -{
      -  "description": "Category slug filter.",
      -  "type": "string"
      -}
    • removedInput schema / properties / freshness
      Removed value: -{
      -  "description": "fresh | active | stale_risk (W5 tier; omit for no filter).",
      -  "type": "string"
      -}
    • removedInput schema / properties / geo_verified_only
      Removed value: -{
      -  "description": "Only jobs classified geo_fit = id_friendly (W2).",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / include_region_locked
      Removed value: -{
      -  "description": "Default false. When true, also return jobs restricted to a region an Indonesia-based applicant cannot work from (geo_fit = restricted, or applicant_region in US/UK/EU/Canada/North America). Check each row's `indonesiaEligibility` before recommending one.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / job_type
      Added value: +{
      +  "description": "full-time | part-time | contract | freelance",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "1–50 (default 20).",
      +  "type": "integer"
      +}
    • addedInput schema / properties / locale
      Added value: +{
      +  "description": "id | en (default id).",
      +  "type": "string"
      +}
    • addedInput schema / properties / location
      Added value: +{
      +  "description": "Location text filter.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Result offset for pagination.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / opportunity_type
      Added value: +{
      +  "description": "regular | internship | fellowship | apprenticeship | volunteer | gig (default: regular)",
      +  "type": "string"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Free-text query (title, company, skills).",
      +  "type": "string"
      +}
    • removedInput schema / properties / query
      Removed value: -{
      -  "description": "Free-text query matched against title/company.",
      -  "type": "string"
      -}
    • addedInput schema / properties / remote_type
      Added value: +{
      +  "description": "worldwide | regional | timezone-based",
      +  "type": "string"
      +}
    • removedInput schema / properties / remote_usd_only
      Removed value: -{
      -  "description": "Only worldwide-remote jobs paid in USD.",
      -  "type": "boolean"
      -}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return shape ('basic job fields + an apply URL') and a monetization caveat about promoted listings on the free tier, but says nothing about pagination behavior, rate/quota limits beyond the 'free tier' hint, or result ordering.

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?

Three tight sentences, front-loaded with purpose and scope, each adding distinct information (scope, return shape, sponsored caveat). 'Basic job fields' is the only slightly imprecise phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a no-required-param search tool: it covers purpose, return contents, and a caveat, and the schema handles parameter detail. It omits result ordering, pagination strategy, and any sibling routing, which leaves an agent with gaps for an eight-parameter tool.

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 pagination via offset. The description adds only marginal semantic value through the 'Indonesia-friendly' framing, which loosely relates to locale/location but does not clarify how parameters interact.

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 (Search) and resource (jobs) with a narrowing scope: 'active remote / Indonesia-friendly'. An agent can distinguish it from get_job (single job) and talent_search (candidates) by scope, 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 Guidelines3/5

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

The domain scope implies when to use it ('remote / Indonesia-friendly jobs'), but there is no explicit when-not guidance and no routing to alternatives such as get_job for a known job ID. Usage must be inferred from the scope phrase.

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