{"version":"2.1.319","anchor":"prompt-for-published-pages-connector-tool-availability-guid","canonical_anchor":"prompt-for-published-pages-connector-tool-availability-guid","heading":"Published pages are told to check which connector tools a viewer has","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/prompt-for-published-pages-connector-tool-availability-guid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Published pages are told to check which connector tools a viewer has\n\nClaude's guidance for published pages now says to list available connector tools and show a feature as unavailable when its tool is missing or blocked\n\n**What**\n\nWhen Claude builds a published page that uses a connector (a link to an outside service), its instructions now say more than that the connector's tools are available. They tell the page to:\n\n- call `listTools()` after the viewer has allowed the connector\n\n- expect that a viewer may have fewer tools than the author\n\n- show a feature as unavailable when its tool is not listed or a call is rejected with `blocked_by_policy`\n\n**Why**\n\nPages Claude writes should now cope with viewers whose access is narrower, for example because of an organization policy, instead of breaking when a tool is missing.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}