Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Build profile from CV text

import_cv_text
Destructive

Fallback when you cannot read the CV yourself: Jobiba's rules parser reads pasted CV text (phone, place, links, notice period, work preference, summary, skills, roles, education, certifications, languages). Without apply=true it only returns a preview; with apply=true it fills empty fields and adds new list items without overwriting anything. Returns applied, kept and skipped fields (including roles found without dates).

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": {
      "text": "<text>"
    },
    "name": "import_cv_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesFull CV text.
applyNotrue only after the user approved the preview.
replaceSummaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare a write operation with destructiveHint=true, and the description earns credit by refining that: without apply the call is a preview only, with apply it fills empty fields and appends list items rather than overwriting, and the response reports applied, kept and skipped fields. This tells the agent exactly what state changes and what will not be touched, notably that roles without dates may be skipped.

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?

Three sentences, front-loaded with the fallback condition and the preview/apply distinction, with no filler. The long parenthetical field list is dense but conveys which parsers exist; it could be trimmed since the response's applied/kept/skipped report already surfaces results.

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 no output schema, the description usefully summarizes return categories (applied, kept, skipped) and the merge semantics, which is enough for an agent to call it correctly. The only material hole is the undocumented replaceSummary flag in an otherwise write-capable, non-idempotent tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%; the description adds real meaning for apply (preview versus commit, plus the approval gate) and clarifies what text is fed to the parser. However, the third parameter, replaceSummary, is never mentioned in the description and has no schema description, which is a notable gap given the description's emphasis on 'without overwriting anything'.

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 ('Jobiba's rules parser reads pasted CV text') and scopes it as a fallback for pasted text rather than uploaded files, which separates it from import_profile_from_cv and import_my_uploaded_cv. The parenthetical enumerates exactly which fields are parsed, so an agent knows what output to expect.

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?

Gives a clear selection rule ('Fallback when you cannot read the CV yourself'), which effectively tells the agent to prefer its own reading or the file-based importers first, and adds a two-step workflow gate ('true only after the user approved the preview'). It stops short of naming the sibling tools or stating explicitly when not to use it.

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.