Skip to main content
Glama

Fitbit Sleep Logs

fitbit_list_sleep
Read-onlyIdempotent

Retrieve your Fitbit sleep logs with pagination and date filtering. Supports privacy modes to control data exposure.

Instructions

List Fitbit sleep logs. Supports before/after cursor, pagination and privacy modes. Requires sleep scope. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoFitbit page number.
afterNoReturn records after this calendar date. Converted to Fitbit afterDate; mutually exclusive with before.
limitNoFitbit per_page value. Fitbit allows up to 200.
beforeNoReturn records before this calendar date. Converted to Fitbit beforeDate; mutually exclusive with after.
all_pagesNoFetch multiple pages up to max_pages.
max_pagesNoMaximum pages to fetch when all_pages is true.
privacy_modeNoOptional per-call privacy override. Defaults to FITBIT_PRIVACY_MODE or structured. raw returns upstream Fitbit JSON. summary minimizes sensitive health and profile details.
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
recordsYes
endpointYes
has_moreYes
next_pageNo
privacy_modeYes
pages_fetchedYes
Behavior4/5

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

Annotations already mark it read-only, idempotent, non-destructive. Description adds requirement for sleep scope, privacy mode handling, and a medical disclaimer, providing additional behavioral context beyond annotations.

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

Conciseness5/5

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

Two sentences: first states purpose, second lists capabilities and requirements. No wasted words, front-loaded with essential information.

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?

Given the output schema exists, the description need not explain return values. It covers key features and constraints (scope, privacy, pagination) adequately for a list operation. Could elaborate on pagination behavior, but sufficient.

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 coverage is 88% with detailed parameter descriptions. The description summarizes key parameters (page, before/after, pagination, privacy) but adds no new meaning beyond the schema.

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

Purpose5/5

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

The description clearly states 'List Fitbit sleep logs' with specific verbs and resource. It distinguishes from siblings like fitbit_get_sleep_day by highlighting support for cursors, pagination, and privacy modes.

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

Usage Guidelines3/5

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

Provides prerequisites ('Requires sleep scope') and capabilities but lacks explicit when-not-to-use or direct alternatives. Usage context is implied but not exclusionary.

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

Install Server

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/fitbit-mcp'

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