Skip to main content
Glama
fauguste

boondmanager-mcp-server

by fauguste

Supprimer une référence (expérience pro)

boond_resources_reference_delete
Destructive

Delete a professional experience reference from a resource's profile. Reads current list, removes the specified reference, and updates the profile. Irreversible action, verify reference ID first.

Instructions

Supprime une référence (expérience professionnelle) du DT d'une ressource. Read-modify-write : lit la liste actuelle, en retire la référence ciblée, republie le reste. ⚠️ Action irréversible — vérifier l'ID au préalable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceIdYesID de la ressource portant la référence (les references sont embarquées dans le DT).
referenceIdYesID de la référence à supprimer.
Behavior5/5

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

The description discloses the read-modify-write pattern ('lit la liste actuelle, en retire la référence ciblée, republie le reste') and explicitly states irreversibility (⚠️ Action irréversible). Annotations already have destructiveHint: true, but the description adds valuable detail beyond 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?

Three sentences, front-loaded with purpose, then behavior details, then critical warning. Every sentence adds value, and the structure is clear and efficient.

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?

The description covers the core behavior, the read-modify-write nature, and the irreversible action. For a simple delete tool with two parameters and no output schema, this is largely complete. However, it could mention the return value (e.g., success message or void) for full completeness.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds context that references are embedded in the DT, but both parameters are already well-described in the schema (resourceId and referenceId). No additional semantics beyond the schema are provided.

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 the action ('Supprime une référence'), the resource ('du DT d'une ressource'), and differentiates from siblings (create/update) by specifying deletion. The title also includes 'Supprimer une référence (expérience pro)', reinforcing the purpose.

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 includes the warning 'vérifier l'ID au préalable', implying usage after verifying the reference exists. It does not explicitly state when not to use, but the warning provides context. No alternative tools are mentioned explicitly, but siblings (create/update) are clear from the context.

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