Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Get Jobiba job details

get_job
Read-onlyIdempotent

Retrieve one active Jobiba vacancy by jobId or slug: sanitized full description, published salary, skills, location and canonical URL. Inactive or expired postings are not returned.

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": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
jobIdNo

Output Schema

NameRequiredDescriptionDefault
jobYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / job / 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

A3.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, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real context beyond them: results are active-only, the description text is sanitized, and the specific fields returned are listed.

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?

Two sentences, no filler, with the resource and return contents front-loaded before the eligibility caveat. The field list is dense but each item is informative.

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?

An output schema exists, so return values need no further explanation, and the active-only constraint is covered. The remaining gap is the required-parameter question: with zero required fields, the agent is not told whether jobId, slug, or either is needed to make a valid call.

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 0% and both parameters are marked optional, yet the description names jobId and slug and frames them as alternative lookup keys, which is more than the schema conveys. It does not state that at least one must be supplied, what happens if both are given, or any slug format.

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?

The description gives a specific verb plus resource ('Retrieve one active Jobiba vacancy by jobId or slug') and enumerates the returned payload (description, salary, skills, location, canonical URL). It is clearly a single-record fetch, distinct from siblings like save_job or apply_to_job, though it never names an alternative 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 verb and the lookup keys; there is no explicit when-to-use statement or pointer to a search/list alternative. The one boundary it does supply is that inactive or expired postings are not returned, which usefully tells the agent what a miss means.

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.