feat(agent-toolkit): support docOwnerIds in create_doc tool

[Noa-Reuven]

https://monday.monday.com/boards/3713040192/pulses/11854345358

Summary

Add optional docOwnerIds input to the create_doc tool schema — same pattern as PR #335 did for create_board.

Problem

When a personal agent creates a doc, it becomes the doc owner — but it cannot subsequently add the agent owner as a subscriber/member. The reason: the platform performs a dual permission check (agent_permission ∩ agent_owner_permission). Since the agent owner has no access to the newly created doc, this intersection is empty and the invite is blocked.

Fix

The create_doc (board) creation mutation supports passing board_owner_ids as input. Ownership subscription happens inside the mutation itself, bypassing the permission checks that would block a subsequent call. By exposing this parameter in the MCP tool, agents can add the agent owner as a co-owner at creation time.

Changes

• create-doc-tool.ts — add optional docOwnerIds: string[] field to the tool schema
• create-doc-tool.graphql.ts — pass $docOwnerIds → board_owner_ids in the createDoc mutation
• graphql.ts — add docOwnerIds to CreateDocMutationVariables type (mirrors how PR feat(agent-toolkit): support owners in create_board tool #335 updated CreateBoardMutationVariables)
• create-doc-tool.test.ts — tests for with/without docOwnerIds

Usage

{
  "location": "workspace",
  "workspace_id": 123,
  "doc_name": "My Doc",
  "markdown": "# Hello",
  "docOwnerIds": ["<agent_owner_user_id>"]
}

Note

npm run codegen should be run to regenerate types from the live schema and verify that board_owner_ids is accepted by the create_doc mutation. The graphql.ts change was made manually following the same pattern as PR #335.

References

• PR feat(agent-toolkit): support owners in create_board tool #335 (create_board owners): feat(agent-toolkit): support owners in create_board tool #335
• Slack discussion: https://monday.slack.com/archives/C0AUFD1AKFA/p1778057163233509
• Requested by: Andrey Palman

---

🤖 Generated with Claude Code

[SergeyRoyt]

Several of the changed files (graphql.ts, gql.ts, schema.graphql, schema.dev.graphql) are codegen-generated. The PR notes the edits were made manually — the generated AST blob in graphql.ts is especially fragile to maintain by hand. Should run npm run codegen before merging to verify the schema accepts doc_owner_ids and replace the manual edits with the real generated output.

[RomKadria]

Update version