Skip to content

feat(agent-toolkit): document the "group" filter column - #481

Merged
stasshw merged 1 commit into
masterfrom
feat/get-board-items-page-group-filter
Sep 6, 2026
Merged

feat(agent-toolkit): document the "group" filter column#481
stasshw merged 1 commit into
masterfrom
feat/get-board-items-page-group-filter

Conversation

@stasshw

@stasshw stasshw commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator

What

Documents the group filter column in three places. Descriptions only — no filtering behavior or schema-shape change.

  • get_board_items_page description: a GROUP FILTERING section with the exact rule to use.
  • filters[].columnId: states that group is accepted alongside real board column ids.
  • get_column_type_info: returns filter guidelines for columnType: "group" (previously filter: null).

Why

Filtering by group has always worked — filters: [{"columnId": "group", "compareValue": ["group_mm6wsvcc"]}] — but it was documented nowhere, and get_board_info does not return group among a board's columns. Models could only get it right from prior knowledge of the monday API.

Meanwhile includeGroup hands the model each item's group.id. With no documented way to filter on it, models put the group id in filters[].columnId and got "Column not found".

Effect

Over 2 days, monday-agents caller:

  • 21% of the tool's ResourceNotFoundException (500 of 2,367) — 40% excluding one runaway tenant
  • 191 accounts affected
  • 81% of failed group filters then scanned the whole board (351 of 431, ~2.9 extra calls each)

Notes

  • Started larger and cut twice, deliberately. A groupIds parameter was dropped because the capability already exists in filters, a parameter is a permanent API commitment while a description is free to change, and groupIds next to columnIds would read like a projection rather than a filter. A server-side repair of misplaced group ids was dropped because it rewrites caller intent with nothing logged, and its value on top of the descriptions is unmeasured.
  • Plan: re-measure this error code on the dashboard after release. Add a parameter or a repair only if the failures persist, with data behind it.
  • The guidance says to use any_of / not_any_of for filtering by group id, rather than claiming those are the only supported operators — rule-engine-board-columns-config.json lists 10 for the group column. It recommends an array of ids without requiring one, since filter_rules_service.rb:70 applies Array.wrap.
  • Group-only on purpose. Not here: the other non-column ids (__item_id__, __creation_log__, __last_updated__, 177 failures), oversized error messages, the hosted-mcp schema copy.
  • 5.67.0 → 5.68.0. 1,336 tests pass.

🤖 Generated with Claude Code

@stasshw
stasshw force-pushed the feat/get-board-items-page-group-filter branch 3 times, most recently from eebe023 to 1460d63 Compare September 6, 2026 13:05
@stasshw stasshw changed the title feat(agent-toolkit): add groupIds to get_board_items_page feat(agent-toolkit): document the "group" filter column Sep 6, 2026
Filtering items by board group has always worked - filters:
[{"columnId": "group", "compareValue": ["group_mm6wsvcc"]}] - but it was
documented nowhere: not in the tool description, not in the input schema,
and get_board_info does not return "group" among a board's columns.
Models could only get it right from prior knowledge of the monday API.

That produced 21% of get_board_items_page's ResourceNotFoundException
errors across 191 accounts. includeGroup hands the model each item's
group.id, and with no documented way to filter on it, models put the
group id in filters[].columnId and got "Column not found". In 81% of
those cases the model then abandoned filtering and paged the whole board.

Descriptions only, no schema or behaviour change:

- get_board_items_page description gains a GROUP FILTERING section with
  the exact rule to use
- filters[].columnId states that "group" is accepted
- get_column_type_info returns filter guidelines for columnType "group",
  which previously returned filter: null

Whether documentation alone is enough will be measured on the same
dashboard before adding any parameter or server-side repair.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@stasshw
stasshw force-pushed the feat/get-board-items-page-group-filter branch from 1460d63 to bff838f Compare September 6, 2026 13:12
@stasshw
stasshw merged commit dc2cf48 into master Sep 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants