jules-mcp

Overview Schema Source Related Servers Discussions Admin

jules_rebase_pr

Rebase an existing GitHub PR onto the latest base branch locally and force-push with lease to eliminate PR collision and out-of-date branch warnings.

Instructions

Rebase an existing Jules GitHub PR against the latest base branch (e.g. main) locally and force-push with lease, eliminating PR collision and out-of-date branch warnings on GitHub.

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": {
      "repo_path": "<repo_path>",
      "pr_url_or_number": "<pr_url_or_number>"
    },
    "name": "jules_rebase_pr"
  }
}

Input Schema

Name	Required	Description
`repo_path`	Yes	Absolute local repository path.
`base_branch`	No	Base branch to rebase onto (defaults to 'main').
`pr_url_or_number`	Yes	GitHub PR URL or number to rebase.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Sep 5, 2026

TDQS

A3.9/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. It discloses the key behavior: rebasing locally and force-pushing with lease, which implies history rewriting. However, it does not mention potential conflicts, required working-tree state, permission implications, or what happens on failure. The force-push-with-lease detail helps but is not fully comprehensive.

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?

A single, dense sentence that front-loads the core operation, includes the method (force-push with lease), and states the intended outcome. No filler or redundant information.

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?

For a mutation tool with no annotations and no output schema, the description covers the high-level operation and rationale but omits practical details such as conflict handling, prerequisite local repository state, and failure behavior. It is adequate for an informed agent but not fully complete.

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 coverage is 100%, so the baseline is 3. The description adds the context that rebase targets the latest base branch and mentions 'main' as an example, which mildly reinforces base_branch semantics, but it does not meaningfully expand on repo_path or pr_url_or_number beyond what the schema already states.

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 action (rebase), the resource (an existing Jules GitHub PR), the target (latest base branch), and the mechanism (local rebase followed by force-push with lease). It clearly differentiates from sibling tools like jules_merge_pr because it is explicitly about rebasing rather than merging.

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 identifies the concrete scenario for use: eliminating PR collision and out-of-date branch warnings on GitHub. It does not explicitly mention when not to use it or compare against sibling alternatives, but the intended trigger conditions are clear.

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