Skip to main content
Changes state - verify before retry Adds a real PDF or text FILE to a knowledge base and indexes it — the same import the dashboard upload performs. This is NOT a read-only action. Use it after create_upload_url (kind kb_document, target_id = kb_id) once the user has uploaded the file: pass the upload_id. In hosts that attach chat files to tools (ChatGPT), the host fills in file for a document the user attached; leave it alone otherwise. For text you already have in the conversation use upload_knowledge_base_text instead — never base64-encode a PDF yourself. Titles must be unique within the knowledge base.

Parameters

Complete input schema

Registered output schema

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, title.
  • Provide one file source: a host attachment, a completed upload_id, or supported inline content. The optional file fields are alternatives; omitting all of them does not submit a file. See MCP file uploads.

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.
Successful results include structuredContent and a text content block containing the same JSON. Check isError first, then read structuredContent or parse content[0].text. See MCP responses and errors for the full envelope and failure behavior.

Verify the result

Confirm the response is not marked isError. Call 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.