Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Rechercher des webhooks

boond_webhooks_search
Read-onlyIdempotent

Search and list BoondManager webhooks by keywords to retrieve their IDs and labels. Returns one-line summaries; use for enumeration when ID is unknown. Read-only.

Instructions

Liste et recherche les webhooks de BoondManager, par mots-clés et pagination.

Quand : pour retrouver l'ID d'un(e) webhook à partir de son nom, ou pour énumérer les webhooks existant(e)s. Plutôt que : boond_webhooks_get si l'ID est déjà connu — la recherche ne renvoie qu'un résumé d'une ligne par webhook.

Returns : page de résumés (ID + libellé principal), plus structuredContent.total = nombre total côté BoondManager. Lecture seule.

  • fields : projection côté MCP, jamais transmise à l'API — remplace le résumé par les seuls attributs listés (noms inconnus ignorés). À utiliser sur les grosses pages.

  • Pagination sans effet : cette route renvoie toujours la table complète, pageSize et page sont ignorés par l'API — inutile de paginer, tout est déjà là.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNuméro de page (défaut: 1, max: 100)
fieldsNoProjection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.
keywordsNoMots-clés de recherche (nom, email, compétences...)
pageSizeNoNombre de résultats par page (max: 500, défaut: 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNombre d'éléments retournés sur cette page
itemsYes
totalNoNombre total de résultats côté BoondManager

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.12.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv2.9.0
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Projection : attributs à afficher par résultat (ex: ['title','updateDate']). Absent = résumé standard. Noms inconnus ignorés.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. Changed1 schema field changedv2.7.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Nombre d'éléments retournés sur cette page",
+      "type": "number"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attributes": {
+            "additionalProperties": {},
+            "description": "Attributs projetés (présent si `fields` est fourni)",
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "id": {
+            "type": "string"
+          },
+          "summary": {
+            "description": "Résumé standard (absent si `fields` est fourni)",
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Nombre total de résultats côté BoondManager",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "items"
+  ],
+  "type": "object"
+}
  4. First observedv2.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations readOnlyHint, openWorldHint, and idempotentHint, the description discloses critical behavior: the API always returns the complete table, page and pageSize are ignored, and fields is only a local MCP-side projection that is never sent to the API. This non-obvious behavior would otherwise require experimentation and is exactly what an agent needs.

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?

Each sentence serves a distinct purpose: listing, reading when to use it, naming the alternative, describing the output, and explaining parameter caveats. The information is compact, well segmented, and the most important caveat pagination ignored is clearly marked.

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 fully-optional search tool with an annotated schema, output schema, and read-only annotations, the description covers purpose, when/when-not, output shape, and all non-obvious parameter behavior. No decision-relevant information appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema already covers all parameters, the description adds essential meaning: it warns that pagination is ineffective and that `fields` only controls local projection, taking an unchanged field list. This directly changes how an agent should fill the parameters and prevents pointless pagination calls.

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: 'Liste et recherche les webhooks de BoondManager.' It explicitly separates this from boond_webhooks_get by noting search returns one-line summaries and is for finding an ID by name, so an agent can select the right tool without opening schemas.

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' section defines exact use cases (retrieve webhook ID from name, or enumerate webhooks), and the 'Plutôt que' section names boond_webhooks_get as the alternative when the ID is already known. It also states why that alternative is preferable, leaving no ambiguity.

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

Deploy Server

Other Tools