Skip to main content
Glama
georgeracu

google-jules-mcp-server

by georgeracu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Jules Sources

jules_list_sources

Lists GitHub repositories connected to Jules. Requires the Jules GitHub app to be installed for repositories to appear.

Instructions

List all GitHub repositories connected to Jules. You must install the Jules GitHub app at https://jules.google.com before repositories appear here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoAIP-160 filter expression to narrow the results (e.g. by repo owner)
pageSizeNoNumber of sources to fetch per page (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • addedInput schema / properties / pageSize / default
      Added value: +50
    • changedInput schema / properties / pageSize / description
      Previous value: -"Number of items per page"New value: +"Number of sources to fetch per page (default: 50)"
    • removedInput schema / properties / pageToken
      Removed value: -{
-  "description": "Token for pagination to get the next page",
-  "type": "string"
-}
  2. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / filter
      Added value: +{
+  "description": "AIP-160 filter expression to narrow the results (e.g. by repo owner)",
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully discloses that results depend on the GitHub app being installed, but it does not describe output shape, pagination behavior, or explicitly confirm read-only behavior beyond the verb 'List'.

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 concise sentences: the purpose is front-loaded, and the critical prerequisite is stated in the second sentence. There is no repetition of schema fields or unnecessary detail.

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 list operation with two optional, well-documented parameters, the description and schema together are nearly complete. The main gap is the lack of return-format details, but that is minor for an intuitive list-repositories operation.

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%, with clear descriptions for both filter and pageSize, so the baseline is 3. The tool description adds no parameter-specific meaning beyond what the input schema already provides.

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 states a specific verb and resource: 'List all GitHub repositories connected to Jules.' It clearly clarifies that 'sources' are GitHub repositories, distinguishing this from the sibling session, schedule, and activity tools.

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 conveys a clear prerequisite: the Jules GitHub app must be installed before repositories appear. It does not explicitly contrast this with jules_get_source or other alternatives, but the 'List all' scope and installation context give a clear sense of when to use it.

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