_list_workspaces returns incomplete results unless searchTerm is provided

[heecheon92]

Summary

The monday MCP list_workspaces behavior appears inconsistent.

In my session, calling _list_workspaces without searchTerm returned only a single workspace, even though the authenticated account has access to many more. When I called the same tool with a searchTerm, the response included a disclaimer saying the search term was not applied, but it then returned the broader/full workspace list.

This makes the unfiltered workspace listing unreliable.

Steps to Reproduce

1. Call _list_workspaces with:

   • limit: 10
   • page: 1

2. Call _list_workspaces with:

   • limit: 100
   • page: 1

3. Call _list_workspaces with:

   • limit: 100
   • page: 1
   • searchTerm: "<any string>"

Actual Result

Unfiltered call

Only one workspace was returned:

{
  "message": "Workspaces retrieved",
  "data": [
    {
      "id": "<workspace-id-1>",
      "name": "<workspace-name-1>",
      "url": "https://<tenant>.monday.com/workspaces/<workspace-id-1>"
    }
  ]
}

This happened for both:

limit=10, page=1
limit=100, page=1
Call with searchTerm
The response said the search term was not applied, but returned a much larger list including the expected workspaces:

{
  "message": "Workspaces retrieved",
  "disclaimer": "Search term not applied - returning all workspaces. Perform the filtering manually.",
  "data": [
    { "id": "<workspace-id-a>", "name": "<workspace-name-a>" },
    { "id": "<workspace-id-b>", "name": "<workspace-name-b>" },
    { "id": "<workspace-id-c>", "name": "<workspace-name-c>" },
    { "id": "<workspace-id-d>", "name": "<workspace-name-d>" }
  ]
}

Expected Result

Calling _list_workspaces without searchTerm should return the full accessible workspace list, subject only to normal pagination.

Adding a searchTerm should either:

actually filter results, or
behave identically to the unfiltered listing
It should not change the completeness of the result set.

Notes

This does not appear to be a simple pagination issue.
page: 2 on the unfiltered call returned no workspaces.
The issue appears to be specific to the MCP tool behavior, not the monday account itself, since the broader list is accessible through the same integration when searchTerm is present.
Impact
This can cause clients/agents to incorrectly conclude that only one workspace is accessible, which breaks discovery and follow-up actions against the correct workspace.
This behavior occured on vscode codex extension with ChatGPT Monday Connector integration.

Workaround

As a temporary workaround, calling _list_workspaces with any searchTerm seems to force the broader result set, even though the response says the search term is ignored.