Box MCP Write Tools Appear in Schema but Return “Tool Not Found” at Runtime

I can independently reproduce the same issue with the Box connector in ChatGPT.

Environment:
- Box account: Individual
- ChatGPT Box connector: connected successfully
- ChatGPT connector permission setting: "Allow all actions"

The following write operations work correctly:
- upload_file — SUCCESS
- create_folder — SUCCESS
- create_file_comment — SUCCESS
- copy_file — SUCCESS

However, the following tools are exposed in the ChatGPT tool/schema definitions, but fail at runtime:

- upload_file_version
  MCP error -32602: Tool upload_file_version not found

- get_upload_url
  MCP error -32602: Tool get_upload_url not found

- update_file_properties
  MCP error -32602: Tool update_file_properties not found

I also tested additional existing-item mutation operations:

- update_folder_properties
  MCP error -32602: Tool update_folder_properties not found

- move_file
  MCP error -32602: Tool move_file not found

The test file itself reports these Box permissions:
- canUpload: true
- canRename: true
- canDelete: true
- canComment: true
- canShare: true

So this does not appear to be a general Box write-permission issue. Creating new files/folders, copying files, and adding comments all succeed. The failures are specifically occurring for multiple tools that modify existing Box items.

I also performed a comparison using the Box connector in Claude. In Claude, upload_file_version, get_upload_url, and update_file_properties are not exposed in the connector schema at all, while upload_file works successfully.

So the behavior differs between clients:

- ChatGPT: these tools are exposed in the schema, but return "Tool not found" at runtime.
- Claude: the same tools are not exposed in the schema.

This makes me suspect there may be a mismatch between the tool catalog/schema exposed to the client and the tools actually registered or available at runtime.

Could someone from Box please confirm:

1. Whether upload_file_version, get_upload_url, update_file_properties, update_folder_properties, and move_file are currently expected to work with the ChatGPT Box connector for Individual accounts.
2. Whether there is any known issue with the MCP tool registry/tool exposure for these write tools.
3. Whether this behavior depends on Box plan, Tool Access configuration, or the specific AI client.

I am happy to provide additional reproduction details if needed.

I can reproduce the issue described in this thread with the Box connector in ChatGPT.

My workflow is to retrieve a PDF attachment from Microsoft Outlook and archive it in a specific Box folder. The Outlook connector successfully retrieves the attachment, and the Box connector can:

• Search for folders and files

• List folder contents

• Read file and folder metadata

• Create a new folder

However, uploading the PDF requires the get_upload_url tool. Although this tool is exposed in the ChatGPT tool schema, every invocation returns:

MCP error -32602: Tool get_upload_url not found

The affected file is a normal two-page PDF of approximately 49 KB. I retried the operation several times on September 16, 2026, fetched a fresh copy of the Outlook attachment, and confirmed that the destination folder exists and is empty. The result remained unchanged.

This does not appear to be related to the file size, file type, Box connection, or general write permissions, because folder creation works correctly. The failure seems limited to the binary-upload tool advertised in the schema but unavailable at runtime.

Could Box please confirm:

1. Whether get_upload_url is currently supported by the Box connector in ChatGPT.

2. Whether this is a known mismatch between the exposed tool schema and the tools registered at runtime.

3. Whether there is a supported workaround for uploading binary files such as PDFs.

4. Whether and when a fix is expected.

At present, this issue prevents automated archiving of Outlook PDF attachments in Box, even though all preceding workflow steps work correctly.

I’m running into these issues too, both for `get_upload_url` and `get_download_url`, and this is now impacting several teams who require use of these Box MCP tools for their work. Both of these tools are verified as enabled in the OpenAI Admin Console too.

Please advise.

Hello Box team,

Could you please help route this report to the Box MCP engineering team for investigation?

I reproduced the same issue on October 1, 2026, with two separate Box connections in ChatGPT, including the official Box connector. Disconnecting and reconnecting did not resolve it.

Working:
- Authentication and file/content reads
- File metadata reads
- Uploading new files

Failing despite being exposed in the ChatGPT tool schema:
- upload_file_version
- get_upload_url
- update_file_properties
- move_file

Example error:
MCP error -32602: Tool upload_file_version not found

The affected existing files report canUpload=true, canRename=true, and canDelete=true.

Updating existing Box files worked in my workflow previously. This now blocks a critical part of my daily work. Creating new files does not meet the workflow's needs, because it depends on preserving existing file IDs and links.

Since several users have provided independent reproductions in this thread, I would appreciate a Box staff acknowledgment and confirmation of whether the issue is being tracked by the appropriate engineering team.

Could you please clarify:
1. Are these tools expected to be available in the hosted Box MCP runtime used by ChatGPT?
2. Can you share an issue reference or the team handling the investigation, if available?
3. Is there a supported workaround that updates existing files while preserving their IDs?
4. Is there an estimated restoration timeline, or a next update we can look out for?

The observed behavior suggests a mismatch between the advertised tools and runtime availability; I have not established where that mismatch originates.

Thank you for your help investigating and routing this to the appropriate team.

I can confirm a related problem from the Claude side, on a free Individual Box account. One clarification first, to avoid confusion: in Claude, upload_file IS available, but upload_file_version is NOT.

- upload_file only creates a NEW file (new file ID). According to its tool description, it returns an error if a file with the same name already exists in the folder, so it cannot replace the content of an existing file.
- upload_file_version (upload a new version of an existing file, keeping its file ID and links) is what I used to use. It is no longer exposed to Claude at all.

Timeline:
- Until around the end of August 2026, I could overwrite existing files by file ID with upload_file_version through the Claude Box connector.
- Around mid-September 2026 I noticed it was gone. As of October 2, 2026 it is still missing. Disconnecting and reconnecting the connector did not change this.

What the Claude connector exposes now:
- The connector's settings list only six write/delete tools: Copy File, Copy Folder, Create File Comment, Create Folder, Create Metadata Template and Upload File (upload_file).
- There is no tool to update an existing item: upload_file_version, update_file_properties and move_file are not listed.
- Reading files/folders and searching work. Creating new files with upload_file works (I tested it today).

So this matches the reports above (existing-item tools unavailable, new-item tools fine), except that in Claude the tools are absent from the tool list, while in ChatGPT they are listed and then return "Tool not found". I have not established where this originates.

Like the previous poster, I depend on preserving file IDs and links, so creating new files is not a workable alternative.

The Box MCP tools documentation lists upload_file_version as Default: Off (an admin must enable it), but a free Individual account has no Admin Console. Could Box staff please confirm:
1. Did the default for these write tools change recently, and is that intended for Individual accounts?
2. Is there any way for an Individual account to enable them?
3. Is this being tracked by the MCP engineering team?

Thank you.