I am using langchain, when I see "click" tool was called, the error is quite often: ToolException: No snapshot found. Use browser_snapshot to capture one

[XinyueZ]

File /opt/venv/lib/python3.12/site-packages/langchain_mcp_adapters/tools.py:58, in _convert_call_tool_result(call_tool_result)
     55     tool_content = tool_content[0]
     57 if call_tool_result.isError:
---> 58     raise ToolException(tool_content)
     60 return tool_content, non_text_contents or None

ToolException: No snapshot found. Use browser_snapshot to capture one

[OrKoN]

The client is expected to call take_snapshot first as click requires an input based on the snapshot. The message is not correct though, the tool was renamed from browser_snapshot to take_snapshot. We expect the client to make additional calls based on the error message that guides the client. So the exception is expected here. I am not familiar with langchain but why does it fail instead of continuing? it seems most clients would continue and adapt based on the error message? Thanks for filing the report and for insights into langchain.

[OrKoN]

The spec says that business logic errors should be reported as isError response: https://modelcontextprotocol.io/specification/2025-06-18/server/tools#error-handling so it sounds like the fix should be on the langchain side?

[Sauravdas007]

I want to work on this issue as i am familiar with Langchain framework .

[XinyueZ]

I met this issue because of this issue

[mw418]

i am also using langchin. When I execute click, it always returns "no snapshot found ..." but I’ve already take snapshot. Have you encountered this?

[OrKoN]

Can you reproduce the issue with https://github.com/modelcontextprotocol/inspector?

[mw418]

Can you reproduce the issue with https://github.com/modelcontextprotocol/inspector?

i can not reproduce.