jules-mcp

Overview Schema Source Related Servers Discussions Admin

jules_reply_feedback

Send feedback, clarification, or steering instructions to a paused or in-progress session to unblock tasks or redirect output.

Instructions

Send user feedback, unblocking clarification, or follow-up steering instructions directly to an in-progress or paused session.

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": {
      "session_id": "<session_id>",
      "message": "<message>"
    },
    "name": "jules_reply_feedback"
  }
}

Input Schema

Name	Required	Description	Default
`message`	Yes	Your instruction, answer to Jules' question, or steering feedback.
`session_id`	Yes	The session ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Sep 5, 2026

TDQS

A4/5.0

Behavior3/5

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

The description clearly states the core action: sending a message directly to a session. However, with no annotations, it does not disclose additional behavioral details such as whether sending resumes the session, whether it can be called multiple times, or what error/response behavior to expect.

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?

One efficient sentence with no filler. The action and target are front-loaded, and the message-type list earns its place by clarifying exactly what the tool is for.

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 two-parameter tool with full schema coverage and no output schema, the description provides enough context to select and invoke it correctly. It could mention post-conditions, but the target context and purpose are clear.

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% and the schema already describes both parameters sufficiently. The description does not add parameter-specific details, but the baseline of 3 applies because the schema does the heavy lifting.

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 uses a specific verb ('Send'), names the resource ('in-progress or paused session'), and enumerates the message types (feedback, clarification, steering). This clearly distinguishes it from sibling tools that check events, create tasks, or approve plans.

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?

It gives clear context for when to use the tool: when sending user feedback, unblocking a clarification, or providing follow-up steering. It does not explicitly name alternatives or exclusion cases, but the target session state is specified.

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