Google Sheets MCP Tool returning 404 errors

LangSmith Product Help Agent Builder
1

I am using the hosted Agent Builder and trying to use the google_sheets_get_spreadsheet and read_range tools. I am consistently getting 404 Requested entity was not found errors, even though:

  1. The Spreadsheet exists and is valid.

  2. I have shared the sheet explicitly with the service account (langchain-tool-user@...) as Editor.

  3. I even tested with a public “Anyone with the link” sheet.

Any idea what I am missing?

2

Hi,

Just a few clarifying questions.

Can you connect to google sheets via oauth in the agent builder settings?

Are other tools working and just these specific google sheets ones aren’t?

When you say hosted, are you using the self hosted version of Agent Builder?

3

Thank you Eric.

Seems like yes since I found this:
CONNECTED INTEGRATIONS

GoogleTools: google_sheets_read_range +2 more

Connected

Yes, the other tools (Slack reply and read thread) are working. The agent reported through Slack chat that it was getting 404 from Sheets.

The AI agent wrote that answer and I didn’t revise properly, sorry, my bad. I’m using the smith.langchain.com Agent Builder plataform on my browser.

4

tools.json

{
“tools”: [
{
“name”: “google_sheets_read_range”,
“mcp_server_url”: “https://tools.langchain.com”,
“mcp_server_name”: “Agent Builder”,
“display_name”: “google_sheets_read_range”
}
],
“interrupt_config”: {
“https://tools.langchain.com::google_sheets_read_range::Agent Builder”: false
}
}

In the Tracing…
google_sheets_read_range

Input
{‘range’: ‘DB_SCADA!1:3’, ‘spreadsheet_id’: ‘1cld[…entire spreadsheet id…]Yz40UQ’}
Raw Output
output:
additional_kwargs: {}
artifact: null
content: ‘{“success”: false, “error”: “Failed to read Google Sheets range: <HttpError 404 when requesting https://sheets.googleapis.com/v4/spreadsheets/1cld[…entire spreadsheet id…]Yz40UQ/values/DB_SCADA!1%3A3?alt=json returned “Requested entity was not found.”. Details: “Requested entity was not found.”>”}’
id: 78aaada7-def5-4422-8f16-0662e5055912
name: google_sheets_read_range
response_metadata: {}
status: success
tool_call_id: 81e0b517-624b-49cb-99e3-e8befd6abbb4
type: tool

5

Workaround.

As a test I asked to the agent to create a spreadsheet and it did it (only possible in the root of Google Drive). After that I wrote something in that sheet and asked the agent to read range in the spreadsheet it created and it worked, the agent brought me what I wrote there.

So I transferred all my data to that sheet and have been working with that since then.