boondmanager-mcp-server

Modifier un(e) candidat

boond_candidates_update

Idempotent

Update an existing candidate's record by ID in BoondManager. Provide only the fields to change; remaining candidate details stay unchanged, enabling partial updates for candidate information.

Instructions

Met à jour un(e) candidat existant(e), identifié(e) par son ID.

Quand : pour modifier quelques champs d'un enregistrement déjà en base. Plutôt que : boond_candidates_create si l'enregistrement n'existe pas encore.

Mise à jour partielle : seuls les champs fournis sont écrits, les autres sont laissés en place.
Attention aux champs de type tableau, qui sont remplacés et non fusionnés.

Returns : confirmation et fiche mise à jour.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	ID du candidat à modifier
`city`	No	Ville
`note`	No	Notes
`state`	No	État du candidat
`title`	No	Titre / fonction
`email1`	No	Email principal
`phone1`	No	Téléphone
`country`	No	Pays
`lastName`	No	Nom
`firstName`	No	Prénom
`mainSkills`	No	Compétences principales

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Identifiant de l'entité créée/modifiée
`type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.15.0Sep 10, 2026

changedInput schema / properties / email1 / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

Changed2 schema fields changedv2.12.2Aug 14, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedv2.7.0Jun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Identifiant de l'entité créée/modifiée",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv2.1.0May 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavioral details: the update is partial, only provided fields are written, and absent fields are left untouched. It also warns that array fields are replaced rather than merged, and states the return payload: confirmation and the updated candidate record. These details are not contained in the annotations.

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 description is compact and well structured: core behavior first, then a clear 'Quand' section, an alternative-tool note, and a short bullet list. Every line provides actionable information, and the return value is included without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage, the presence of an output schema, and the annotations, this description is complete enough for correct invocation. It covers the update scenario, partial-update behavior, the create alternative, and the response, so an agent can decide when to call it and how to interpret the result.

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 description coverage is 100%, so each parameter is already documented in the schema. The description adds valuable cross-parameter semantics by clarifying that omitted optional fields are not cleared, and that provided fields are written as part of the partial update. This goes slightly beyond the baseline but does not deeply explain individual parameter formats.

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 the exact operation: update an existing candidate identified by its ID. It explicitly distinguishes the tool from the sibling creation tool by saying 'Plutôt que : boond_candidates_create si l'enregistrement n'existe pas encore.' This removes ambiguity about whether to use update or create.

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?

The 'Quand' clause clearly indicates this is for modifying specific fields of an existing record. The 'Plutôt que' clause names the alternative tool and its condition of use: if the record does not exist yet, use boond_candidates_create. This gives the agent a clear decision rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server