google-jules-mcp-server

by georgeracu

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List Jules Sessions

jules_list_sessions

List all Jules sessions with their current states to locate session IDs or track multiple coding tasks at a glance.

Instructions

List all your Jules sessions with their current states. Useful for finding session IDs or checking on multiple tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`pageSize`	No	Number of sessions per page (default: 10)
`pageToken`	No	Token for pagination to get the next page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

A3.9/5.0

Behavior3/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 read-only listing behavior and that states are included, but it does not clarify pagination behavior (e.g., 'all' may require multiple pages) or any other constraints. This is a minor transparency gap.

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 two sentences, front-loaded with the action ('List all your Jules sessions') and includes a practical use case. Every word earns its place, with no redundant information.

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?

The tool is simple, but with no output schema and no annotations, the description only partially covers return values ('current states') and does not mention pagination semantics. It is adequate for basic selection but not fully complete without additional inference.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional parameter information, meaning no extra credit for clarifying semantics beyond the schema.

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 uses a specific verb 'List' with the resource 'Jules sessions' and adds 'with their current states', making it clear what the tool does. This distinguishes it from siblings like jules_create_session or jules_get_status, which have different purposes.

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 provides clear context by stating 'Useful for finding session IDs or checking on multiple tasks', indicating when to use the tool. It does not explicitly mention alternatives or exclusions, but the use case is well implied.

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