boondmanager-mcp-server

Créer un(e) opportunité

boond_opportunities_create

Create a new opportunity in BoondManager, for adding records that do not yet exist. Search first to avoid duplicate entries, then create with company, dates, contacts, and revenue details.

Instructions

Crée un(e) opportunité dans BoondManager.

Quand : pour ajouter un(e) opportunité inexistant(e). Plutôt que : boond_opportunities_update pour modifier un enregistrement existant, et boond_opportunities_search d'abord pour vérifier qu'il n'existe pas déjà.

Écriture réelle et non idempotente : deux appels identiques créent deux enregistrements (l'API ne déduplique pas).
Les ID de relations et les états/types sont des ID numériques BoondManager, à résoudre au préalable (recherches d'entités, boond://dictionary/*).

Returns : confirmation, ID créé, et la fiche complète. structuredContent.id est réutilisable directement pour chaîner un appel.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Nom / titre de l'opportunité
`note`	No	Description de l'opportunité (mappée sur /data/attributes/description)
`state`	No	État de l'opportunité
`poleId`	No	ID du pôle (relation pole)
`typeOf`	No	Type d'opportunité : ID numérique du dictionnaire setting.typeOf.project (ex: 1, 3), via boond_application_dictionary
`endDate`	No	Date de fin prévue (YYYY-MM-DD)
`agencyId`	No	ID de l'agence (relation agency)
`criteria`	No	Critères / compétences recherchées (texte libre). Alimente le matching de boond_workflow_candidats_pour_opportunite.
`companyId`	No	ID de la société cliente (relation company)
`contactId`	No	ID du contact associé (relation contact)
`startDate`	No	Date de début prévue (YYYY-MM-DD ou 'immediate')
`hrManagerId`	No	ID de la ressource responsable RH (relation hrManager)
`expertiseArea`	No	Domaine d'expertise : ID du dictionnaire setting.expertiseArea (via boond_application_dictionary)
`mainManagerId`	No	ID de la ressource responsable principal / commercial (relation mainManager)
`turnoverEstimatedExcludingTax`	No	Chiffre d'affaires estimé HT (montant)

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.

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#"

Changed14 schema fields changedv2.7.0Jun 19, 2026

addedInput schema / properties / agencyId

Added value: +{
+  "description": "ID de l'agence (relation agency)",
+  "type": "string"
+}

changedInput schema / properties / companyId / description

Previous value: -"ID de la société cliente"New value: +"ID de la société cliente (relation company)"

changedInput schema / properties / contactId / description

Previous value: -"ID du contact associé"New value: +"ID du contact associé (relation contact)"

addedInput schema / properties / criteria

Added value: +{
+  "description": "Critères / compétences recherchées (texte libre). Alimente le matching de boond_workflow_candidats_pour_opportunite.",
+  "maxLength": 5000,
+  "type": "string"
+}

addedInput schema / properties / expertiseArea

Added value: +{
+  "description": "Domaine d'expertise : ID du dictionnaire setting.expertiseArea (via boond_application_dictionary)",
+  "type": "string"
+}

addedInput schema / properties / hrManagerId

Added value: +{
+  "description": "ID de la ressource responsable RH (relation hrManager)",
+  "type": "string"
+}

addedInput schema / properties / mainManagerId

Added value: +{
+  "description": "ID de la ressource responsable principal / commercial (relation mainManager)",
+  "type": "string"
+}

changedInput schema / properties / note / description

Previous value: -"Notes / description"New value: +"Description de l'opportunité (mappée sur /data/attributes/description)"

addedInput schema / properties / note / maxLength
```
Added value: +65000
```

addedInput schema / properties / poleId

Added value: +{
+  "description": "ID du pôle (relation pole)",
+  "type": "string"
+}

changedInput schema / properties / startDate / description

Previous value: -"Date de début prévue (YYYY-MM-DD)"New value: +"Date de début prévue (YYYY-MM-DD ou 'immediate')"

addedInput schema / properties / turnoverEstimatedExcludingTax

Added value: +{
+  "description": "Chiffre d'affaires estimé HT (montant)",
+  "type": "number"
+}

addedInput schema / properties / typeOf

Added value: +{
+  "description": "Type d'opportunité : ID numérique du dictionnaire setting.typeOf.project (ex: 1, 3), via boond_application_dictionary",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

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.7/5.0

Behavior4/5

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

While annotations already set idempotentHint=false, the description adds valuable behavioral context by stating it is a real, non-idempotent write and that two identical calls create two records because the API does not deduplicate. It also warns that relation/state/type IDs must be resolved beforehand, which goes beyond the structured 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 well structured and front-loaded with the core action, followed by labeled sections for when to use, alternatives, behavioral warnings, and return value. Every sentence earns its place and there is no redundant filler.

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?

For a create operation with 15 parameters, the description covers when to use it, which sibling tools to prefer instead, non-idempotence implications, ID resolution requirements, and the shape of the response including a directly reusable ID. Combined with the full input schema and output schema, this gives an agent the context needed to select and invoke the tool 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 description coverage is 100%, so the baseline is 3. The description adds extra semantic guidance beyond the schema by explaining that relation IDs and state/type values are numeric BoondManager IDs to be resolved in advance via entity searches and boond://dictionary/*, which clarifies a whole class of parameters. It also notes that structuredContent.id can be reused for chaining, adding practical value.

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 opens with a clear verb and resource: 'Crée un(e) opportunité dans BoondManager.' It further distinguishes itself from siblings by naming boond_opportunities_update for modifications and boond_opportunities_search for pre-existence checks, so an agent can easily tell when this create tool is the right choice.

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?

Explicit usage guidance is provided: use it to add a non-existent opportunity ('Quand : pour ajouter un(e) opportunité inexistant(e)'), and explicitly route to update for existing records and search first to verify non-existence. This is strong when-to-use vs. alternative guidance.

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

Deploy Server