google-jules-mcp-server

Overview Schema Source Related Servers Discussions Admin

Get Jules Session Output

jules_get_session_output

Retrieve final output and pull request details from a completed Jules session, providing the results needed after task completion.

Instructions

Retrieve the final output and results from a completed Jules session, including pull request details. Use after session state is COMPLETED.

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

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Session ID to get output for

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 states the return includes 'final output and results' and 'pull request details,' and implies a prerequisite that the session be completed. However, it does not disclose error behavior if used prematurely, auth requirements, or guarantee of non-mutation. Adequate but not rich.

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, and contains no redundant or filler text. It earns its place with the specific mention of 'pull request details' and the completion prerequisite.

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 simple tool with one parameter and no output schema, the description adequately covers the purpose and usage condition. It could be more complete by explaining what happens if the session is not completed, but given the low complexity, it is nearly complete, earning a 4.

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 parameter 'sessionId' is already described as 'Session ID to get output for.' The description does not add additional semantic meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 action ('Retrieve the final output and results'), the resource ('from a completed Jules session'), and even includes specific content ('including pull request details'). It distinguishes itself from sibling tools by specifying the post-completion context, differentiating it from get_status and list_sessions.

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 explicitly says 'Use after session state is COMPLETED,' providing clear timing guidance. It does not mention when not to use it or alternative tools, but the completion prerequisite is a strong usage guideline, earning a 4.

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