Skip to main content
Glama
georgeracu

google-jules-mcp-server

by georgeracu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Jules Session Activities

jules_list_activities

Retrieve a detailed activity log for a Jules session, including plan generation, progress updates, messages, and completion events, with most recent activities first.

Instructions

Get detailed activity log for a Jules session. Activities include plan generation, progress updates, messages, and completion events. Most recent activities appear first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of activities to retrieve (default: 10)
sessionIdYesSession ID to get activities for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • removedInput schema / properties / pageToken
      Removed value: -{
-  "description": "Token for pagination to get the next page",
-  "type": "string"
-}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It implies a read-only operation (listing) and notes ordering ('most recent first'), but does not explicitly state that it has no side effects or mention any constraints like authorization or rate limits.

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 highly concise, consisting of two sentences that pack the essential action, purpose, and behavior. It is front-loaded with the main verb and contains no redundant or extraneous information.

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?

The description covers the essential context: what is returned (activity log), what types of activities are included, and the ordering. It does not describe the response format or error handling, but for a simple read operation this is adequate.

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?

Both parameters (sessionId and limit) are already described in the schema with clear meanings. The tool description adds no extra semantic detail beyond the schema, such as how limit interacts with the ordering or any additional constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get detailed activity log') and resource ('a Jules session'), and implies a collection via 'activity log'. It is distinguishable from the sibling 'jules_get_activity' (singular), though it doesn't explicitly say 'list'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'jules_get_activity' for a specific activity or 'jules_list_sessions' for sessions. The description does not mention any selection criteria or comparison.

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

Deploy Server

Other Tools