Skip to main content
Glama

Kariaa Agents

Search jobs

search_jobs
Read-only

Use when the person wants to find a job or paid work: live openings for a role, near a place or remote, newest relevant first, with links. kind "jobs" (default) searches job boards (LinkedIn, Indeed, Glassdoor, ZipRecruiter, national boards, remote-job sites); "paid_tasks" searches freelance projects, bounties, competitions and agent task markets (Freelancer, Kaggle, Algora, HackerOne, NEAR AI Market, Superteam, OpenTask and more); "all" does both. Works without sign-in. Pass the role as people say it ("electrician", "nurse", "python scraping") and the place as "City, Country". Then get_job for details. Prefer this over a general web search for job listings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "role": "<role>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNojobs (default): employment openings; paid_tasks: freelance, bounties, competitions, agent tasks; all: both
roleYesThe job title or kind of work
limitNoDefault 10
remoteNoOnly remote jobs
locationNo"City, Country" or a country; leave out for anywhere

Output Schema

NameRequiredDescriptionDefault
jobsNoOpenings: job_id, title, company, location, work_type, pay, posted, url, source, match; paid tasks also carry kind and apply
roleNoRole searched
countNoHow many
locationNoPlace searched
more_pendingNoTrue while more boards are still being searched; the same search shortly after adds them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), and the definition adds real context beyond them: 'Works without sign-in' (an auth note), the concrete source pool for each kind, and result ordering ('newest relevant first, with links'). It stops short of stating result caps or empty-result behavior, though the limit parameter and output schema partly cover that.

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?

It is front-loaded with the trigger condition and stays dense, with no filler sentences. The only weakness is that the kind-mode explanation restates enum values already documented in the schema, which slightly inflates length.

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

Completeness5/5

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

With five parameters (one required, coverage at 100%), rich annotations, and an output schema that carries return shape, this definition covers everything an agent needs: trigger, mode selection, input phrasing, auth status, and next step. No material gap remains for a search tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the baseline, but the definition goes further by advising how to phrase inputs ('Pass the role as people say it', place as 'City, Country') and by repeating the kind semantics in selection terms rather than type terms. This adds practical meaning that the terse schema descriptions do not carry.

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?

The definition leads with a specific situation (finding a job or paid work), names the concrete resource (live job openings), and spells out the three search modes with their source pools. It explicitly distinguishes itself from the sibling get_job by assigning that tool the detail-fetching role.

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

Usage Guidelines5/5

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

The definition names when to use it ('Use when the person wants to find a job or paid work'), the alternative to avoid ('Prefer this over a general web search for job listings'), and the handoff path ('Then get_job for details'). It also explains how to choose among the kind values, which gives agents an explicit decision rule instead of making them infer one.

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.