openwebui-mcp-server

openwebui_get_chat

Retrieve a chat's complete details and all messages by its unique ID. Find the ID via chat list or search.

Instructions

Get full details of a specific chat by ID, including all messages in the conversation. Use openwebui_list_chats or openwebui_search_chats to find chat IDs.

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": {
      "id": "<id>"
    },
    "name": "openwebui_get_chat"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Chat ID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It reveals that the tool returns full details and all messages, which is helpful, but it does not explicitly mention important behavioral aspects such as read-only status, authentication requirements, or error behavior. Since 'get' implies a read operation, the gap is not severe, but more explicit disclosure would be beneficial.

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 sentences: the first states the core function, the second provides practical guidance for finding IDs. Every sentence earns its place with no wasted words, and the purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool without an output schema, the description adequately conveys the main content (chat details and messages) and gives a path to discover IDs. It is complete enough for an agent to select and invoke the tool correctly.

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?

The input schema already documents the single 'id' parameter completely with a description. The description only says 'by ID', which adds no new semantic detail beyond the schema. Given 100% schema coverage, the baseline of 3 is appropriate.

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 clearly states the tool's function: retrieving full details of a specific chat by ID, including all messages. This distinguishes it from sibling tools like list_chats (which lists chats) and search_chats (which finds by query), and it specifies the resource and scope.

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 explicitly directs users to openwebui_list_chats or openwebui_search_chats to find chat IDs, providing clear context for when to use this tool (when an ID is known) versus alternatives. It does not explicitly state exclusions, but the context is strong enough.

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