Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Apply to a job

apply_to_job
DestructiveIdempotent

Apply to a job with a chosen resume. For Jobiba-native jobs the first call returns a preview and sends nothing; the application is submitted, with the resume attached as a PDF snapshot, only when called again with confirm=true. For jobs that use an external employer form it returns Jobiba's apply link (it opens the employer's form for the signed-in user), a resume download and a details kit instead, and with markApplied=true records the user's own application in their tracker.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYes
confirmNoOnly true after the user explicitly approved sending this application.
resumeIdNoResume to send (from tailor_resume_for_job or list_my_resumes).
markAppliedNoExternal jobs: record that the user applied on the employer site.
screeningAnswersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already indicate a destructive, open-world, non-read-only operation, but the description adds critical behavior beyond them: the first native call sends nothing, submission only happens with confirm=true, the resume is attached as a PDF snapshot, and external jobs return an apply link plus a details kit. That is exactly the kind of mutation semantics an agent needs.

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?

The definition is dense but front-loaded: it starts with the core action and then explains native versus external flows in order. Every clause carries behavioral information, with no redundant restatement 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?

For a complex mutation with no output schema, the description explains the important return behaviors — preview, apply link, resume download, details kit — and the two application flows. The main remaining gap is screeningAnswers, which is undocumented despite being part of the input contract.

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 description adds useful meaning for confirm and markApplied and explains the resume attachment behavior, while schema descriptions already cover resumeId, confirm, and markApplied. However, screeningAnswers is neither described in the schema nor mentioned in the description, so a meaningful parameter remains unexplained.

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?

The description states a specific verb and resource — applying to a job with a chosen resume — and clearly distinguishes Jobiba-native applications from external employer-form applications. An agent can tell what the tool does and how the two modes differ without opening the schema.

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

Usage Guidelines4/5

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

It gives clear operational guidance: native jobs require a first preview call and then confirm=true to submit, while external jobs return an apply link and can record the application with markApplied=true. It lacks explicit routing to sibling tools such as prepare_complete_application, but the mode-selection guidance is strong.

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.