gemini-pro-mcp

Overview Schema Source Related Servers Discussions Admin

jules_sessions

Read-only

List your recent Jules sessions newest first to find a session ID or see which tasks are still running. Pass an ID to jules_status, jules_approve_plan or jules_message.

Instructions

List the user's most recent Jules sessions, newest first, to find a session id or see which tasks are still running. Read-only and free.

    Pass an id from the result to jules_status for details, to
    jules_approve_plan or to jules_message.

    Args:
        limit: How many sessions to list (default 10).

    Returns:
        One line per session: id, state (as Jules reports it, for example in
        progress, awaiting plan approval or completed) and title, or
        "No sessions yet."

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so 'Read-only and free' partly restates structured data, but 'free' adds a cost signal the annotations don't carry. The description also discloses the return shape and enumerates the state values Jules may report, which is real behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose in the first sentence, then routing, then structured Args/Returns blocks. Slightly padded by the redundant 'Read-only and free' clause, but no sentence is otherwise wasted.

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 one-parameter read tool, the description covers purpose, when to use, sibling routing, the parameter, and expected output including the empty case. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 0%, so the description must supply meaning — it explains that 'limit' controls how many sessions are listed and that it defaults to 10. That fills the documentation gap for the only parameter, though it omits bounds or maximum allowed values.

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 and resource ('List the user's most recent Jules sessions'), plus ordering ('newest first') and the two concrete reasons to call it. It is clearly distinguishable from siblings like jules_status, which returns details for a single id.

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?

Gives explicit when-to-use conditions (find a session id, see which tasks are running) and routes the agent onward: pass an id to jules_status, jules_approve_plan, or jules_message. The agent can pick the correct tool from this alone.

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

Deploy Server