{"version":"2.1.317","anchor":"sdk-schema-built-in-tool-page-token-for-artifact-list-pro","canonical_anchor":"sdk-schema-built-in-tool-page-token-for-artifact-list-pro","heading":"Artifact listing can page through results, and tool results say which built-in tool ran","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sdk-schema-built-in-tool-page-token-for-artifact-list-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Artifact listing can page through results, and tool results say which built-in tool ran\n\nListing artifacts now accepts page_token to fetch the next page, and tool-result details gain an optional built_in_tool field\n\n**Unclear.** It is not clear whether the tool actually accepts page_token yet, or only its description mentions it.\n\n**What**\n\nSeveral parts of the data Claude Code exchanges with programs that embed it changed:\n\n- Tool-result details gained an optional `built_in_tool` field.\n\n- The artifacts tool's list action accepts `page_token`, the `next_page_token` an earlier listing of the same scope gave, to list the artifacts after it. Only `limit`, `scope` and `page_token` may go with a list request.\n\n- The description of `server_display_name` was reworded.\n\n- A configuration format gained fields about the program's use case.\n\n**Why**\n\nPrograms embedding Claude Code get more detailed information back, and long lists of artifacts can be read a page at a time.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}