Skip to main content
Glama

journal-delete

Destructive

Delete a journal entry and all its pages — or, with categoryId, only that page category (its pages stay, uncategorized; bridge module 8.19.0+, Foundry 13+). This action cannot be undone!

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": {
      "journalId": "<journalId>"
    },
    "name": "journal-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
journalIdYesThe journal ID to delete
categoryIdNoDelete only this category of the journal (from journal-get), not the journal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / categoryId
      Added value: +{
      +  "description": "Delete only this category of the journal (from journal-get), not the journal",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds real value on top: pages under a deleted category survive as uncategorized, and the category mode requires bridge module 8.19.0+ on Foundry 13+. The version prerequisite is a genuine precondition an agent could otherwise miss; the 'cannot be undone' warning largely restates the destructive annotation.

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?

A single sentence with the default behavior front-loaded, the conditional mode in the middle, and the irreversibility warning at the end. Zero redundant wording.

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 two-parameter destructive tool with full schema coverage and destructive annotations, the description covers the destructive consequence, the conditional semantics, and the version gate. Only the return behavior is unexplored, which is minor for a delete operation without an output schema.

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?

Schema coverage is 100%, so baseline is 3, and the description earns the bump by explaining the consequence of categoryId (its pages remain, uncategorized) rather than merely naming the parameter. It also pins down the version requirement that governs whether the parameter is honored at all.

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 (delete) and resource (journal entry and all its pages), then immediately carves out the alternate mode: with categoryId only the category is removed. An agent can distinguish whole-journal deletion from category-limited deletion without opening the schema.

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 makes the selecting condition explicit — omit categoryId to delete the journal, supply it to delete only a category — which is the primary usage decision for this tool. It does not, however, address when to reach for journal-page-delete instead when individual pages are the target, so the sibling routing is incomplete.

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.

Resources