Skip to main content
Glama

jules_list_tasks

View and filter Google Jules AI coding tasks by status to monitor development progress and manage workflow automation.

Instructions

List all Jules tasks with their status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return (default 10)
statusNoFilter tasks by status

Implementation Reference

  • The core handler function for the 'jules_list_tasks' tool. Loads tasks from local JSON persistence, filters by optional status parameter, limits results, formats a human-readable summary, and returns it as tool content.
    private async listTasks(args: any) {
      const { status = 'all', limit = 10 } = args;
      const data = await this.loadTaskData();
      
      let filteredTasks = data.tasks;
      if (status !== 'all') {
        filteredTasks = data.tasks.filter(task => task.status === status);
      }
      
      const tasks = filteredTasks.slice(0, limit);
      
      const taskList = tasks.map(task => 
        `${task.id} - ${task.title}\n` +
        `  Repository: ${task.repository}\n` +
        `  Status: ${task.status}\n` +
        `  Created: ${new Date(task.createdAt).toLocaleDateString()}\n` +
        `  URL: ${task.url}\n`
      ).join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Jules Tasks (${tasks.length} of ${filteredTasks.length} total):\n\n${taskList || 'No tasks found.'}`
          }
        ]
      };
    }
  • Input schema for the jules_list_tasks tool, defining optional 'status' filter (enum) and 'limit' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        status: {
          type: 'string',
          enum: ['all', 'active', 'pending', 'completed', 'paused'],
          description: 'Filter tasks by status',
        },
        limit: {
          type: 'number',
          description: 'Maximum number of tasks to return (default 10)',
        },
      },
    },
  • src/index.ts:375-376 (registration)
    Registration of the jules_list_tasks handler in the CallToolRequestSchema switch statement.
    case 'jules_list_tasks':
      return await this.listTasks(args);
  • src/index.ts:159-175 (registration)
    Tool descriptor registration in the ListToolsRequestSchema response, including name, description, and schema.
      name: 'jules_list_tasks',
      description: 'List all Jules tasks with their status',
      inputSchema: {
        type: 'object',
        properties: {
          status: {
            type: 'string',
            enum: ['all', 'active', 'pending', 'completed', 'paused'],
            description: 'Filter tasks by status',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of tasks to return (default 10)',
          },
        },
      },
    },
  • Helper method to load persistent task data from JSON file, used by listTasks and other task operations.
    private async loadTaskData(): Promise<{ tasks: JulesTask[] }> {
      try {
        const data = await fs.readFile(this.dataPath, 'utf-8');
        return JSON.parse(data);
      } catch (error) {
        if ((error as any).code === 'ENOENT') {
          return { tasks: [] };
        }
        throw error;
      }
Behavior2/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 states it lists tasks with status, but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'all' entails (e.g., all accessible tasks). For a list tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that front-loads the core action ('List all Jules tasks with their status'). There is zero waste, and it directly communicates the tool's function without unnecessary details.

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?

Given the tool's low complexity (list operation with 2 optional parameters), 100% schema coverage, and no output schema, the description is minimally adequate. However, it lacks context on behavioral aspects (e.g., default behavior, error handling) and doesn't compensate for the absence of annotations, leaving room for improvement.

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%, so the schema fully documents the parameters (limit and status with enum). The description adds no additional meaning beyond implying filtering by status, which is already covered. Baseline 3 is appropriate as the schema does the heavy lifting.

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 verb ('List') and resource ('Jules tasks'), specifying the scope as 'all' with their status. It distinguishes from siblings like jules_get_task (single task) and jules_bulk_create_tasks (creation), but doesn't explicitly differentiate from other list-like tools if they existed. The purpose is specific and actionable.

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. It doesn't mention prerequisites, context for filtering, or compare to siblings like jules_get_task for single tasks or jules_session_info for session-related data. The agent must infer usage from the name and schema alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mberjans/google-jules-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server