Skip to main content
Glama

Oura Sleep Periods

oura_list_sleep
Read-onlyIdempotent

Retrieve Oura sleep period records with sleep stages and timing. Filter by date range to analyze sleep patterns and duration.

Instructions

List detailed Oura sleep period records, including sleep stages and timing where available. Requires the daily scope (Oura has no separate sleep OAuth scope). Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOnly return Oura records after this time. Converted to an Oura start_date.
limitNoMaximum number of records returned by this call, kept from the OLDEST end of the window. Oura v2 serves collections oldest-first, has no sort parameter and no page-size parameter, so limit=1 returns the OLDEST record in the window, never the newest. This domain has no latest-record shortcut resource (only daily readiness has one), so to reach the newest record here, narrow the window with after/before until the response comes back with truncated=false and has_more=false: records are oldest-first, so the LAST one is then the newest that exists in that window. The cap is applied locally after fetching and also stops cursor pagination once it is reached; when it dropped records, truncated is true and has_more is true. If truncated is true, raise limit or set all_pages — do not follow a cursor, because next_token is omitted whenever resuming would skip dropped records.
beforeNoOnly return Oura records before this time. Converted to an Oura end_date.
all_pagesNoWhen true, follow the Oura next_token cursor up to max_pages in this one call. Resume later by passing the returned next_token with the same after/before window.
max_pagesNoMaximum upstream Oura pages to fetch in this call when all_pages is true. A runaway guard, not an Oura page index.
next_tokenNoOpaque Oura v2 cursor from a previous collection response. Pass it back unchanged with the same after/before window to resume. Oura has no integer page index and no page-size parameter; do not invent or increment a page number.
privacy_modeNoOptional per-call privacy override. Defaults to OURA_PRIVACY_MODE or structured. raw returns upstream Oura JSON. summary minimizes sensitive health and profile details.
response_formatNomarkdown
explicit_user_intentNoRequired true when privacy_mode=raw (agent escalation of redaction).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
recordsYes
endpointYes
has_moreYesTrue when more records exist beyond this response, either upstream (a resumable next_token) or because the limit cap dropped records (truncated). If truncated is true, raise limit or set all_pages; if next_token is present, pass it back.
truncatedYesTrue when the limit cap dropped records that had already been fetched. Raise limit or set all_pages (or narrow after/before) to see them. next_token is omitted in this case so a resume cannot skip those rows.
next_tokenNoOpaque Oura v2 cursor to resume from. Pass this back as input next_token with the same after/before window. Present only when more records exist upstream AND this call did not locally drop fetched records (truncated is false). When truncated is true, next_token is omitted: raise limit or set all_pages instead of following a cursor, which would skip the dropped records. Never increment a page number.
privacy_modeYes
pages_fetchedYes
Install Server

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the tool read-only, idempotent, and non-destructive, so the bar for additional behavioral disclosure is lower. The description adds useful context about the OAuth scope requirement and the data-availability caveat ('where available'). It does not describe pagination or output shape, though the limit parameter description compensates substantially.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The top-level description is short and front-loaded with the purpose and content, followed by the auth requirement and a disclaimer. Every sentence earns its place, though 'Not medical advice' is a generic disclaimer that is not directly actionable for tool invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition benefits from a very rich input schema and an output schema, with the limit parameter explaining the hardest behavioral details such as oldest-first ordering and pagination. The description adds the auth prerequisite and availability caveat. The main gap is the lack of an explicit relationship to sibling tools like oura_list_daily_sleep.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high at 89%, and the parameter descriptions are unusually detailed, especially the limit and next_token fields, which explain oldest-first ordering, truncated/has_more semantics, and cursor constraints. The top-level description adds no direct parameter meaning beyond what the schema already provides, so it stays at the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource ('detailed Oura sleep period records') and a clear action ('List'), and mentions the distinguishing content ('sleep stages and timing where available'). It is clear enough, but it does not explicitly contrast this tool with the sibling oura_list_daily_sleep, so differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool over alternatives such as oura_list_daily_sleep or oura_daily_summary. It states the auth prerequisite ('Requires the daily scope') and includes a disclaimer, but no when-to-use or when-not-to-use context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/oura-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server