feat(agent-toolkit): document the "group" filter column - #481
Merged
Conversation
stasshw
force-pushed
the
feat/get-board-items-page-group-filter
branch
3 times, most recently
from
September 6, 2026 13:05
eebe023 to
1460d63
Compare
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
force-pushed
the
feat/get-board-items-page-group-filter
branch
from
September 6, 2026 13:12
1460d63 to
bff838f
Compare
rami-monday
approved these changes
Sep 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents the
groupfilter column in three places. Descriptions only — no filtering behavior or schema-shape change.get_board_items_pagedescription: a GROUP FILTERING section with the exact rule to use.filters[].columnId: states thatgroupis accepted alongside real board column ids.get_column_type_info: returns filter guidelines forcolumnType: "group"(previouslyfilter: null).Why
Filtering by group has always worked —
filters: [{"columnId": "group", "compareValue": ["group_mm6wsvcc"]}]— but it was documented nowhere, andget_board_infodoes not returngroupamong a board's columns. Models could only get it right from prior knowledge of the monday API.Meanwhile
includeGrouphands the model each item'sgroup.id. With no documented way to filter on it, models put the group id infilters[].columnIdand got "Column not found".Effect
Over 2 days,
monday-agentscaller:ResourceNotFoundException(500 of 2,367) — 40% excluding one runaway tenantNotes
groupIdsparameter was dropped because the capability already exists infilters, a parameter is a permanent API commitment while a description is free to change, andgroupIdsnext tocolumnIdswould 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.any_of/not_any_offor filtering by group id, rather than claiming those are the only supported operators —rule-engine-board-columns-config.jsonlists 10 for the group column. It recommends an array of ids without requiring one, sincefilter_rules_service.rb:70appliesArray.wrap.__item_id__,__creation_log__,__last_updated__, 177 failures), oversized error messages, thehosted-mcpschema copy.🤖 Generated with Claude Code