Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Search Jobiba jobs

search_jobs
Read-onlyIdempotent

Search active Jobiba vacancies by role or skill keywords, location, work mode, employment type, experience level and salary range (a salary range needs a currency and pay period). Returns job cards with title, company, location, published pay, skills, a description excerpt and URLs, with paging.

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
sortNo
limitNo
queryNoRole, skill phrase or natural-language keywords; multiple terms are supported.
offsetNo
jobTypeNo
locationNoCity, state, country or supported location query.
salaryMaxNo
salaryMinNo
remoteTypeNo
salaryPeriodNoPay period used with salaryMin or salaryMax; required together with currency for an accurate range.
salaryCurrencyNoCurrency used with salaryMin or salaryMax.
experienceLevelNo

Output Schema

NameRequiredDescriptionDefault
jobsYes
sortYes
limitYes
queryYes
totalYes
offsetYes
hasMoreYes
locationYes
totalExactYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / jobs / items / properties / applyUrl / description
      Added value: +"Jobiba's apply link (https://jobiba.com/apply/{id}) when the job continues on the employer's own form; null when it applies on Jobiba (use url). Never the employer's address."
  2. First observed

TDQS

B3.4/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 fully covered. The description adds the result payload shape (job cards with title, company, location, pay, skills, excerpt, URLs) and paging, but says nothing about result caps (limit max 20, offset max 200), total-count behaviour, or what an empty/no-query search does.

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?

One dense, front-loaded sentence that lists the filter surface before the return-shape clause, plus a short 'with paging' tag. No filler, though the parenthetical salary rule slightly interrupts the enumeration.

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?

With an output schema present the return values do not need explaining, and annotations cover safety, so the description is broadly adequate. Still, for a 12-parameter tool with no required parameters it leaves open the most likely ambiguity: what happens with no query, how paging interacts with sort=relevance vs newest, and whether all filters combine as AND.

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 only 33% across 12 parameters, so the description has real work to do and it does cover the main filter axes plus the salaryMin/Max + currency + period coupling. However that coupling is also already stated in the schema's salaryPeriod and salaryCurrency descriptions, and sort, limit, offset and the five enum-typed filters (jobType, remoteType, experienceLevel, sort) get no explanation beyond the word 'paging'.

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 (active Jobiba vacancies) and enumerates the filter dimensions: keywords, location, work mode, employment type, experience level and salary. It is clearly a discovery/listing tool rather than a detail fetch like get_job, though it never names an alternative to route the agent 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?

Usage is only implied by the nature of a search tool; there is no statement of when to prefer it over sibling tools such as get_job, list_saved_jobs or job_match_score. The one real constraint given ('a salary range needs a currency and pay period') is a parameter rule rather than an when-to-use rule.

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.