Notion

4. Fetch efficiently:

• Search returns ranked page and data-source candidates only. Pick the best candidate, then fetch content with the disclosed Notion fetch tool via useTool using the returned URL or ID.
• If a fetched page clearly points at an inline data source or database, fetch that data source next and work from it.
• If the fetched data source already contains the rows and fields needed to answer, stop there and answer from that result.
• Do not serially fetch many individual row pages when the container page or data source already exposes the needed fields.
• Fetch individual rows only when a small number of important fields are still missing or ambiguous after fetching the canonical page or data source.
• Once you have enough evidence to answer, stop fetching and respond.

Guardrails

• Read-only only.
• Junior intentionally exposes only Notion search and fetch tools for this skill. Do not ask for writes, comments, or page moves.
• Search results may be pages or data sources. Do not treat data sources as unsupported.
• For scoped requests like "US holidays" or "2026 holidays", apply the user's scope when reading the fetched content and state any assumption you made if the source mixes multiple geos or years.
• If search returns no accessible matches, say that no accessible pages or data sources matched and note that the content may be outside the user's Notion permissions or poorly matched by title.
• If content retrieval fails for the top result, return the best matching Notion URL and explain that the result could not be fetched for summarization.