Skip to main content
Glama

Outil.io

Delete sales journey

delete_sales_journey
Destructive

Supprimer définitivement un parcours de vente avec ses visites, prospects, relances en attente et conversions. Les pages, produits, formulaires et workflows liés sont conservés.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_sales_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description goes well beyond that by itemizing exactly what is destroyed (visits, prospects, pending follow-ups, conversions) and exactly what survives (pages, products, forms, workflows). That cascade boundary is precisely the information an agent needs before invoking an irreversible delete and is stated nowhere in the structured fields.

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?

Two sentences, no filler: the destruction scope is front-loaded and the retention clause follows as the natural complement. Every clause carries information an agent would otherwise have to guess.

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?

For a destructive, single-parameter tool with no output schema, the description covers the two things that matter most: irreversibility ("définitivement") and the blast radius. It stops short of stating permission requirements, whether confirmation is mandated, or what the tool returns on success, which would make it fully complete.

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?

There is a single parameter, id, whose meaning is self-evident from the name and whose format is already pinned by the schema pattern (^[a-f0-9]{48}$). The description adds no meaning about what the id identifies or where to obtain it, but with one obvious required parameter the schema carries most of the load.

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?

States a specific verb ("Supprimer définitivement") and a specific resource ("parcours de vente"), then enumerates the dependent entities removed with it. Among the many delete_* siblings, the resource is unambiguous, so an agent can tell it apart from delete_agent, delete_flow, or delete_record without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what the tool does but never when to choose it over an alternative, nor when not to. There is no mention of an archive/disable path, no prerequisite check, and no reference to a sibling such as update_sales_journey for non-destructive changes, so routing must be inferred from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.