google-jules-mcp-server

Overview Schema Source Related Servers Discussions Admin

Delete Jules Session

jules_delete_session

Permanently delete a Jules session by session ID. This irreversible action removes the session; archive instead if you might need it later.

Instructions

Permanently delete a Jules session. This cannot be undone. Use jules_archive_session instead if you may want the session back later.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "jules_delete_session"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Session ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the critical behavioral trait that deletion is permanent and cannot be undone. It could additionally mention side effects (e.g., associated data removal), but the core irreversible nature is clearly stated.

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 wasted words, and the most important information (permanent deletion) is front-loaded. The alternative is provided succinctly.

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 simple delete operation with one parameter and no output schema, the description is complete. It covers purpose, irreversibility, and alternative usage. The sibling context (archive/unarchive) further reinforces the distinction.

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 description coverage is 100%, and the only parameter (sessionId) is already described as 'Session ID to delete.' The tool description adds no extra meaning beyond the schema, which is acceptable given the high coverage and simple single-parameter nature.

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 tool's purpose: 'Permanently delete a Jules session.' It uses a specific verb ('delete') and resource ('session'), and explicitly contrasts with sibling tool jules_archive_session, making differentiation clear.

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?

Provides explicit usage guidance: 'Use jules_archive_session instead if you may want the session back later.' This tells the agent when not to use this tool and names the alternative, making the choice unambiguous.

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