> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Knowledge Base

> Use the update_knowledge_base MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="changes-state"><Badge color="yellow" size="sm" shape="pill">Changes state - verify before retry</Badge></span>

Renames a knowledge base container. This is NOT a read-only action.

## Parameters

| Name    | Type     | Required | Description                                     |
| ------- | -------- | -------- | ----------------------------------------------- |
| `kb_id` | `string` | Yes      | The knowledge base document ID, e.g. kb\_abc123 |
| `name`  | `string` | Yes      | New name for the knowledge base                 |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* Provide the required parameters: `kb_id`, `name`.

## Example MCP request

Send `tools/call` after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_knowledge_base",
    "arguments": {
      "kb_id": "kb_abc123",
      "name": "VALUE"
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/errors) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`. Call [List Knowledge Base Documents](/docs/mcp-tools/knowledge-base/list-knowledge-base-documents) to read the affected resource. Verify that the intended state is visible before making another change.

## Retry safety

This tool changes workspace state. After a timeout, read the affected resource before retrying so you do not create duplicate or conflicting changes.

## Related MCP tools

* [List Knowledge Base Documents](/docs/mcp-tools/knowledge-base/list-knowledge-base-documents): `list_knowledge_base_documents`
* [Get Knowledge Base Document](/docs/mcp-tools/knowledge-base/get-knowledge-base-document): `get_knowledge_base_document`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Knowledge Base MCP tools](/docs/mcp-tools/knowledge-base/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)