Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Update my profile from my CV on Jobiba

import_my_uploaded_cv
Destructive

Reads the CV file the user already uploaded to their Jobiba profile and fills the profile from it with the same rules as import_cv_text. Without apply=true it returns a preview only. If no CV file is on the profile it says so and points to the profile page.

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

Input Schema

NameRequiredDescriptionDefault
applyNotrue only after the user approved the preview.
replaceSummaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare that this is a destructive, non-idempotent write operation, and the description adds useful preview and missing-file behavior. However, it does not explain what profile data gets overwritten or merged, what the preview contains, or what replaceSummary changes, which are important for a destructive tool.

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?

The description is three sentences, front-loads the core action, and efficiently states the preview caveat and missing-file fallback. The reference to 'same rules as import_cv_text' is concise but depends on another tool definition.

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?

It covers the main purpose, apply gating, and missing-file behavior, which is enough for basic invocation. For a destructive profile-write tool with no output schema, it leaves important gaps around affected fields, replaceSummary, and the preview return format.

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

Parameters2/5

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

The apply parameter already has a schema description, and the description mostly reiterates the preview gate. The replaceSummary parameter has no schema description and is not explained in the description, so the 50% schema coverage is not compensated for.

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 states a specific verb and resource: it reads the CV file already uploaded to the user's Jobiba profile and fills the profile from it. The source distinction from import_cv_text is clear, but it does not explicitly differentiate itself from the sibling import_profile_from_cv.

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 explains the key use context: the CV must already be uploaded, apply=true is only for after preview approval, and the missing-file case falls back to the profile page. It does not name an explicit alternative for pasted-text CVs or state broader when-not conditions.

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.