René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"projects_write: item_id parameter typed as float64 instead of string","articleBody":"## Bug Description\n\nThe `projects_write` tool has an ID mismatch between its `add_project_item` and `update_project_item` methods.\n\n`add_project_item` returns a GraphQL node ID (string, e.g. `\"PVTI_lADOBII0s...\"`), but `update_project_item` expects a numeric REST API database ID (`item_id` typed as `number`, parsed via `RequiredBigInt`). This means the ID returned by one method cannot be directly used as input to the other.\n\n## Steps to Reproduce\n\n1. Call `projects_write` with `method: add_project_item` to add an issue to a project\n2. The response returns an `id` like `\"PVTI_lADODr_Ky84BNQJ7zgmwpT4\"` (GraphQL node ID string)\n3. Call `projects_write` with `method: update_project_item`, passing that `id` as `item_id`\n4. The tool rejects it with: `parameter item_id is not of type float64`\n\n## Root Cause\n\nThere are two ID systems at play:\n\n| ID System | Type | Example | Used By |\n|-----------|------|---------|---------|\n| REST API `id` / `fullDatabaseId` | number (int64/BigInt) | `1001` | `update_project_item`'s `item_id` param |\n| GraphQL node `id` | string (ID!) | `\"PVTI_lADOBII0s...\"` | `add_project_item`'s return value |\n\nIn the source (`pkg/github/projects.go`), `item_id` is defined as `Type: \"number\"` and parsed with `RequiredBigInt(args, \"item_id\")`, which is correct for the REST API's numeric ID. However, the return value from `add_project_item` appears to be the GraphQL node ID (string), creating a mismatch.\n\n## Suggested Fix\n\nOne of:\n1. **Preferred:** Have `add_project_item` also return the numeric `fullDatabaseId` so it can be used with `update_project_item`\n2. Have `update_project_item` accept the GraphQL node ID and resolve it to the numeric ID internally\n3. Document which ID format each method expects/returns, so callers know to look up the numeric ID separately\n\n## Workaround\n\nUsing `gh project item-edit` via CLI works fine with the GraphQL node ID string.\n\n## Environment\n\n- MCP endpoint: `https://api.githubcopilot.com/mcp/`\n- Toolset: `default,projects`\n- Client: Claude Code via `mcp-remote`","author":{"url":"https://github.com/leoalord","@type":"Person","name":"leoalord"},"datePublished":"2026-03-05T16:41:24.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2153/github-mcp-server/issues/2153"}