google-jules-mcp-server

Overview Schema Source Related Servers Discussions Admin

Get Jules Session Status

jules_get_status

Check a Jules session's current status and recent activity to poll for progress and completion, as sessions run 5-60 minutes.

Instructions

Check the current status and recent activity of a Jules session. Use this to poll for progress and completion. Sessions typically take 5-60 minutes to complete.

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_get_status"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Session ID to check
`includeActivities`	No	Number of recent activities to include (default: 3)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It adds useful behavioral context by indicating the tool is for repeated polling and the typical duration, implying it's safe to call. However, it does not explicitly state that it is read-only, disclose error behavior, or mention any side effects or permissions needed.

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 core purpose, and includes only essential usage guidance (polling and typical duration). No filler or redundancy.

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?

Given the tool's simplicity (2 params, no output schema, no annotations), the description adequately covers purpose, usage, and typical duration. It lacks mention of return structure or error cases, but the description sets expectations for polling and completion, making it complete enough for most AI agents.

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% for both parameters (sessionId and includeActivities), so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides, except arguably the 'recent activity' phrase aligns with includeActivities, but that's redundant.

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 checks 'current status and recent activity of a Jules session,' which is a specific verb and resource. It differentiates from siblings like jules_get_session_output (which presumably retrieves final output) and jules_list_activities by focusing on session status and polling, while explicitly noting the duration range.

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 gives explicit usage context: 'Use this to poll for progress and completion,' and provides expected time bounds ('Sessions typically take 5-60 minutes'). It does not name alternative tools or state when not to use it, but the context is clear for a polling tool.

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