Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

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. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuine behavioral context beyond them: results are limited to active postings and expired ones are silently absent, plus the note that descriptions are sanitized. It stops short of saying what happens when the id resolves to nothing or when both parameters are supplied.

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 tight sentences, front-loaded with the action and the lookup keys, followed by the returned fields and the active-only constraint. Every clause carries information, though listing the returned fields partly duplicates the output schema.

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 an output schema present, return-shape explanation is not required, and annotations cover safety, so the remaining burden is modest. The description is nearly complete; the one real omission is resolving the ambiguity of two optional parameters that the tool logically needs at least one of.

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%, so the description has to carry parameter meaning; it does name both addressing keys and frames them as alternatives. However, the schema marks neither parameter required, and the description never says that one is needed, which takes precedence if both are given, or what a valid slug looks like — a meaningful gap at zero coverage.

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 uses a specific verb and resource ('Retrieve one active Jobiba vacancy') and enumerates the payload (sanitized description, salary, skills, location, canonical URL), so an agent knows exactly what this returns. It does not explicitly contrast itself with any sibling, but its single-vacancy scope is self-evidently distinct from the saved/alerts/application tools.

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?

It tells the agent the two addressing modes ('by jobId or slug') and states a selection-relevant constraint that inactive or expired postings are not returned. It gives no explicit when-to-use framing versus alternatives such as saved-job listing or match scoring, so usage is only implied.

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.