Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Créer une action

boond_actions_create

Create a new action (call, email, meeting, note) in BoondManager linked to a contact, candidate, resource, opportunity, or project, specifying type, dates, and optional positioning.

Instructions

Crée une nouvelle action (appel, email, RDV, note) dans BoondManager, rattachée à un contact, candidat, ressource, opportunité ou projet (relation dependsOn, obligatoire).

Args:

  • typeOf (number, requis): ID numérique du type d'action (dictionnaire setting.action.*, via boond_application_dictionary)

  • title, text (string, optional): Titre et contenu de l'action

  • startDate, endDate (string, optional): Dates ISO avec timezone (ex: 2026-06-05T10:00:00+0200)

  • contactId | candidateId | resourceId | opportunityId | projectId (string, un requis): Entité de rattachement

  • companyId (string, optional): Société, uniquement en complément d'un contactId

  • positioningId (string, optional): Positionnement à lier — requis par l'API pour les types d'action liés aux positionnements (ex. RQ)

Returns: L'action créée avec son ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoContenu / notes de l'action
titleNoTitre de l'action
typeOfYesType d'action : ID numérique du dictionnaire (setting.action.*, via boond_application_dictionary) ou libellé personnalisé si BOOND_DICTIONARY_OVERRIDES est configuré
endDateNoDate de fin (même format que startDate)
companyIdNoID de la société associée (uniquement en complément d'un contactId)
contactIdNoID du contact auquel rattacher l'action (dependsOn)
projectIdNoID du projet auquel rattacher l'action (dependsOn)
startDateNoDate de début au format ISO 8601 avec timezone (ex: 2026-06-05T10:00:00+0200)
resourceIdNoID de la ressource à laquelle rattacher l'action (dependsOn)
candidateIdNoID du candidat auquel rattacher l'action (dependsOn)
opportunityIdNoID de l'opportunité à laquelle rattacher l'action (dependsOn)
positioningIdNoID du positionnement à lier à l'action (relation positioning). Requis par l'API pour les types d'action liés aux positionnements (ex. RQ) — sans lui, erreur 422 « 1002 - Wrong or missing attribute (/data/relationships/positioning) ».

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed9 schema fields changedv2.7.0
    • addedInput schema / properties / endDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?([+-]\\d{2}:?\\d{2}|Z)?$"
    • addedInput schema / properties / positioningId
      Added value: +{
+  "description": "ID du positionnement à lier à l'action (relation positioning). Requis par l'API pour les types d'action liés aux positionnements (ex. RQ) — sans lui, erreur 422 « 1002 - Wrong or missing attribute (/data/relationships/positioning) ».",
+  "type": "string"
+}
    • changedInput schema / properties / startDate / description
      Previous value: -"Date de début au format ISO avec timezone (ex: 2026-06-05T10:00:00+0200)"New value: +"Date de début au format ISO 8601 avec timezone (ex: 2026-06-05T10:00:00+0200)"
    • addedInput schema / properties / startDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?([+-]\\d{2}:?\\d{2}|Z)?$"
    • addedInput schema / properties / typeOf / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • changedInput schema / properties / typeOf / description
      Previous value: -"Type d'action : ID numérique du dictionnaire BoondManager (setting.action.*, via boond_application_dictionary)"New value: +"Type d'action : ID numérique du dictionnaire (setting.action.*, via boond_application_dictionary) ou libellé personnalisé si BOOND_DICTIONARY_OVERRIDES est configuré"
    • removedInput schema / properties / typeOf / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / typeOf / minimum
      Removed value: -0
    • removedInput schema / properties / typeOf / type
      Removed value: -"integer"
  3. Changed17 schema fields changedv2.2.0
    • changedInput schema / properties / candidateId / description
      Previous value: -"ID du candidat associé"New value: +"ID du candidat auquel rattacher l'action (dependsOn)"
    • changedInput schema / properties / companyId / description
      Previous value: -"ID de la société associée"New value: +"ID de la société associée (uniquement en complément d'un contactId)"
    • changedInput schema / properties / contactId / description
      Previous value: -"ID du contact associé"New value: +"ID du contact auquel rattacher l'action (dependsOn)"
    • removedInput schema / properties / content
      Removed value: -{
-  "description": "Contenu / description",
-  "type": "string"
-}
    • changedInput schema / properties / endDate / description
      Previous value: -"Date de fin"New value: +"Date de fin (même format que startDate)"
    • addedInput schema / properties / opportunityId
      Added value: +{
+  "description": "ID de l'opportunité à laquelle rattacher l'action (dependsOn)",
+  "type": "string"
+}
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "ID du projet auquel rattacher l'action (dependsOn)",
+  "type": "string"
+}
    • changedInput schema / properties / resourceId / description
      Previous value: -"ID de la ressource associée"New value: +"ID de la ressource à laquelle rattacher l'action (dependsOn)"
    • changedInput schema / properties / startDate / description
      Previous value: -"Date de début (YYYY-MM-DD ou ISO)"New value: +"Date de début au format ISO avec timezone (ex: 2026-06-05T10:00:00+0200)"
    • removedInput schema / properties / subject
      Removed value: -{
-  "description": "Sujet de l'action",
-  "type": "string"
-}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Contenu / notes de l'action",
+  "type": "string"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "description": "Titre de l'action",
+  "type": "string"
+}
    • changedInput schema / properties / typeOf / description
      Previous value: -"Type d'action (ex: call, email, meeting, note)"New value: +"Type d'action : ID numérique du dictionnaire BoondManager (setting.action.*, via boond_application_dictionary)"
    • addedInput schema / properties / typeOf / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / typeOf / minLength
      Removed value: -1
    • addedInput schema / properties / typeOf / minimum
      Added value: +0
    • changedInput schema / properties / typeOf / type
      Previous value: -"string"New value: +"integer"
  4. First observedv2.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses important behavioral details: the mandatory dependsOn relation, the positioningId requirement for certain action types (with error 422 note), the companyId-only-with-contactId constraint, and the return of the created action with its ID. This extends well beyond the minimal annotations (all false) to give agents actionable expectations.

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 well-structured with a purpose sentence, an args list, and a return statement. It is moderately long but every line adds value, without fluff.

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 12 parameters and no output schema, the description covers the core purpose, parameter constraints, API caveats (positioning error), and return behavior. It provides sufficient context for an agent to invoke it correctly, even if it lacks full examples.

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?

Though schema coverage is 100%, the description adds crucial relational semantics not visible in the schema: exactly one of contactId, candidateId, resourceId, opportunityId, or projectId is required, companyId pairs only with contactId, and positioningId is API-required for positioning-linked action types. This elevates it above the schema baseline.

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 clearly states it creates a new action (call, email, appointment, note) in BoondManager, specifies the attachable entity types (contact, candidate, resource, opportunity, project), and includes the mandatory dependsOn relation. This distinguishes it from search/get/update/delete siblings.

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?

The description provides clear context on when to use: creating an action tied to any supported entity, and it notes the mandatory dependsOn relation. However, it does not explicitly name alternative tools or exclusion scenarios, which prevents a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fauguste/boondmanager-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server