Graylog MCP Server

delete_log_template

Remove an unwanted learned log template by its ID to keep your Graylog template list clean and accurate.

Instructions

Delete a learned log template by ID.

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": {
      "templateId": "<templateId>"
    },
    "name": "delete_log_template"
  }
}

Input Schema

Name	Required	Description	Default
`templateId`	Yes	Template ID (e.g. tpl_a3f1b2)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.0Aug 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral transparency. While 'Delete' implies a destructive action, it does not disclose whether deletion is permanent, requires special permissions, or has side effects on dependent resources.

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 a single, concise sentence that conveys the essential information without any filler or redundant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple ID-based delete operation with complete schema coverage, the description is minimally viable. However, it lacks context about irreversibility, failure behavior, or consequences when templates are in use, which would be valuable for an agent.

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?

The schema descriptions already fully cover the single parameter with 100% coverage, including an example format. The description adds no additional parameter semantics beyond restating 'by ID', so the baseline of 3 for high schema coverage is appropriate.

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 ('Delete'), the resource ('learned log template'), and the method ('by ID'). It is specific and distinguishes itself from sibling tools like rename_log_template and delete_saved_search.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use delete_saved_search or when a template should be deleted. It does not mention prerequisites like listing templates to obtain a valid ID.

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