Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Add to my profile

add_profile_items
Destructive

Adds facts the user confirmed (skills, experience, education, certifications, languages, target roles and cities) to the profile. Lists only grow: duplicates are skipped and nothing is deleted. A job with no start date is not saved; it is reported back so you can ask the user for it. Returns what was applied, what was kept and what was skipped, 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": "add_profile_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNoProfessional summary. Saved only when the profile has none, unless replaceSummary is true.
skillsNo
educationNo
languagesNo
experienceNo
certificationsNo
replaceSummaryNotrue only when the user asked to replace their current summary.
interestedRolesNo
interestedCitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: lists are append-only, duplicates are skipped, nothing is deleted, and a job with no start date is rejected and reported back. That said, destructiveHint=true is not reconciled—an agent could infer removal is possible, which the description says is not the case; the description never clarifies this tension. It also does not mention auth or rate limits.

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?

Three tight sentences: what it adds, the append-only invariant, the failure mode, and the return shape. No filler, and the most decision-critical constraint (nothing is deleted) is front-loaded.

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 9-parameter mutation tool with no output schema, the description covers the return payload shape (applied/kept/skipped with reasons) and the main failure mode. Missing are deduplication criteria and whether partial success is possible, but overall it is sufficient to call correctly.

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 only 22%, so the description must compensate, and it does add key semantics: the field groups map to parameters, replaceSummary's conditional behavior and the startDate omission rule are explained. It still leaves skills/languages/interestedRoles/interestedCities without format or limit details.

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?

Names the specific verb (adds) and resource (profile), and enumerates the fact types accepted (skills, experience, education, certifications, languages, target roles and cities). This separates it cleanly from get_my_profile/update_my_profile, which read or modify the profile differently.

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?

States the gating condition that facts must be user-confirmed, and implicitly positions this as the additive path versus update_my_profile. It does not explicitly name an alternative tool or say when not to use it, so it stops short of full routing guidance.

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.