Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Update my Jobiba profile

update_my_profile
DestructiveIdempotent

Change fields the user asked to change. Every value is validated (phone, https links, work preference Remote/Hybrid/On-site, visibility). A list you send may only add entries: if it leaves out entries already on the profile nothing is saved, unless replaceLists is true because the user asked to replace that whole list; use add_profile_items to add. An empty string or null clears a text field. Open to work is never confirmed from chat (only the Career Profile toggle confirms it). Date of birth, gender, marital status, pay, coordinates and WhatsApp settings are not accepted. Returns applied, kept and skipped fields with reasons.

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

Input Schema

NameRequiredDescriptionDefault
bioNo
phoneNo
skillsNo
addressNoCity / region / country line.
educationNo
githubUrlNo
languagesNo
experienceNo
openToWorkNo
linkedinUrlNo
noticePeriodNo
openToRemoteNo
portfolioUrlNo
replaceListsNotrue only when the user asked to replace a whole list.
certificationsNo
workPreferenceNo
interestedRolesNo
interestedCitiesNo
profileVisibilityNo
freelancerAvailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only, idempotent write. The description goes beyond them by disclosing the merge semantics (omitted list entries are dropped and nothing is saved unless replaceLists is true), that empty string or null clears a text field, that every value is validated, and that unsupported fields are rejected. It also describes the response (applied/kept/skipped with reasons), which no output schema supplies. Missing only things like permission or rate-limit context.

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?

Dense and front-loaded: the mutation rule and the sibling alternative come first, followed by value semantics, then exclusions, then the return shape. Sentences are long but each carries distinct information; no filler wording is present.

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 destructive 20-parameter write with no output schema and near-zero schema descriptions, the definition covers the highest-risk misunderstandings: list merging, clearing, rejected fields, and what the result contains. Remaining gaps are the formats of the many secondary fields, which an agent can only partly infer.

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 only 10% across 20 parameters, so the description carries real weight — it adds validation rules for phone, https links, workPreference and visibility, plus clearing semantics and the replaceLists rule. However, most parameters (bio, skills, education/experience object shapes, noticePeriod, openToRemote, freelancerAvailable, interestedRoles, interestedCities) get no added meaning, so the compensation is partial.

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 opens with a specific verb-plus-scope statement ('Change fields the user asked to change') and immediately names the sibling it is not ('use add_profile_items to add'), so the agent can tell it apart from add_profile_items. It is slightly indirect about the resource itself — the profile is named in the title rather than the description body — which keeps it from a 5.

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

Usage Guidelines5/5

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

It states explicitly when to use this tool, when to use add_profile_items instead, and the exact condition that unlocks replaceLists ('because the user asked to replace that whole list'). It also gives a hard exclusion ('Open to work is never confirmed from chat') and lists field categories that are out of scope.

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.