Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Create a job alert

create_job_alert
Destructive

Creates a daily or weekly email alert for new matching jobs, sent to the candidate's Jobiba account address. Limit of 10 active alerts. Answers how many live jobs added in the last 7 days match it now and up to 3 of them (title, company, place, URL).

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": {
      "keyword": "<keyword>"
    },
    "name": "create_job_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobTypeNoOptional.
keywordYesRole or skills to watch.
currencyNoCurrency for the salary filter.
locationNoCity or country.
frequencyNoHow often.
remoteTypeNoOptional.
experienceLevelNoOptional.
minAnnualSalaryNoMinimum annual salary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag the write/destructive/non-idempotent profile, and the description adds real context on top: the alert is delivered by email to the account address, there is a 10-alert ceiling, and each call reports how many live jobs from the last 7 days match plus up to 3 samples. It stops short of saying what happens on a duplicate call or whether hitting the limit fails or evicts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the action and delivery target, then the constraint, then the return behavior. No filler or repetition of the title.

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 8 parameters, no output schema, and a mutation annotation set, the description covers the key gaps an agent needs — delivery mechanism, quota, and response shape. A note on duplicate-creation behavior would close the last gap given idempotentHint=false.

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 each parameter including the four enums is already documented in the schema. The description only echoes the frequency notion ('daily or weekly') and adds no matching syntax, salary format, or location-matching rules beyond the schema.

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?

States a specific verb and resource ('Creates a ... email alert for new matching jobs') plus the delivery channel (candidate's Jobiba account address) and cadence, which cleanly separates it from the sibling delete/update/list_job_alert 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?

Gives a useful precondition — 'Limit of 10 active alerts' — but never says when to use this versus update_job_alert for changing an existing alert, or what to do at the cap. Usage is implied rather than directed.

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.