Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Save a job

save_job
Destructive

Save an active job to the candidate's Jobiba saved list.

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": {
      "jobId": "<jobId>"
    },
    "name": "save_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJobiba job ID (the id field from search_jobs or list_my_jobs).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds only that the target is the candidate's personal saved list, and does not explain the non-idempotent behavior (what happens when the job is already saved) or how to undo the destructive effect. This is not a contradiction — nothing in the text claims a safe read — but the behavioral surplus is thin.

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 short sentence, front-loaded with the action verb and the target collection. It is appropriately sized but slightly redundant with the title "Save a job" and could carry one more clause of guidance at no real length cost.

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?

For a one-parameter tool with annotations and no output schema, the description covers the core action adequately. It leaves gaps that matter for a destructive, non-idempotent mutation: behavior on an already-saved job, and the availability of unsave_job to reverse it.

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?

The single jobId parameter is fully documented in the schema, including where to obtain it (search_jobs or list_my_jobs). With 100% schema coverage the baseline of 3 applies; the description adds no format, validation, or edge-case detail about the identifier beyond what the schema states.

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 ("Save") and resource ("job") plus the destination ("candidate's Jobiba saved list"), so an agent can tell it writes to a saved-jobs collection. It does not name or distinguish itself from the obvious sibling unsave_job or clarify the boundary with apply_to_job, leaving some ambiguity about which save-like action to pick.

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

Usage Guidelines2/5

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

The only guidance is the implicit precondition baked into "an active job", which suggests inactive/expired jobs cannot be saved. There is no statement of when to prefer this over apply_to_job or list_saved_jobs, and no mention of the inverse unsave_job path for reversing the action.

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.