Withings MCP

Withings Heart Records

withings_list_heart

Read-onlyIdempotent

Retrieve available Withings heart records within a date range, with pagination and privacy controls.

Instructions

List Withings heart records where available. Requires user.metrics scope. Not medical advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Withings page number.
`after`	No	Inclusive start bound. Converted to Withings startdate (epoch) or startdateymd (YYYY-MM-DD) per action.
`limit`	No	Upstream page-size hint and local output cap used for pagination safety.
`before`	No	Inclusive end bound. Converted to Withings enddate (epoch) or enddateymd (YYYY-MM-DD) per action.
`all_pages`	No	Fetch multiple pages up to max_pages.
`max_pages`	No	Maximum pages to fetch when all_pages is true.
`privacy_mode`	No	Optional per-call privacy override. Defaults to WITHINGS_PRIVACY_MODE or structured. raw returns upstream Withings JSON. summary minimizes sensitive health and profile details.
`response_format`	No		markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`empty`	No
`records`	Yes
`warning`	No
`endpoint`	Yes
`has_more`	Yes
`next_page`	No
`privacy_mode`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.4Sep 4, 2026
- addedOutput schema / properties / empty
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / warning
```
Added value: +{
+  "type": "string"
+}
```
Addedv0.4.11Jul 30, 2026
Removedv0.4.8Jul 17, 2026

Changed3 schema fields changedv0.4.7Jul 6, 2026

changedInput schema / properties / after / description

Previous value: -"Only return Withings records after this time. Converted to an Withings start_date."New value: +"Only return Withings records after this time. Converted to Withings startdate."

changedInput schema / properties / before / description

Previous value: -"Only return Withings records before this time. Converted to an Withings end_date."New value: +"Only return Withings records before this time. Converted to Withings enddate."

changedInput schema / properties / limit / description

Previous value: -"Local page-size hint used for pagination safety."New value: +"Upstream page-size hint and local output cap used for pagination safety."

First observedv0.4.6Jun 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations: the 'Requires user.metrics scope' auth requirement and the 'where available' caveat indicating that heart data may not always be present. It also includes a 'Not medical advice' disclaimer. These go beyond the structured metadata, though it does not detail pagination or rate-limit behavior, which are minor given the annotation coverage.

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?

The description is three sentences with zero waste. The purpose is front-loaded, and the auth requirement and disclaimer follow. Every sentence earns its place; it is appropriately sized for a list tool with rich schema metadata.

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

Completeness3/5

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

The tool has 8 parameters and an output schema, and annotations cover safety, so the description need not repeat those. However, it lacks explicit usage guidance relative to sibling tools (e.g., when to choose heart records over sleep or activity lists) and does not mention pagination behavior beyond what schema hints imply. The description is minimal but adequate given the structured metadata; still, the missing usage context leaves a gap for a tool with many siblings.

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 88% (7 of 8 parameters have descriptions), so the schema already documents the parameters thoroughly. The description adds no parameter-specific information, which is acceptable given the high coverage. Per the rubric, baseline is 3 when schema coverage is high, and the description does not compensate beyond that.

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 states a specific verb ('List') and resource ('Withings heart records'), and adds the qualifier 'where available' to indicate conditional availability. It clearly differentiates from sibling list tools like withings_list_body_measures and withings_list_activity by naming the specific data type. The purpose is unambiguous.

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?

The description provides a clear context: it requires the user.metrics scope and notes that heart records may not always be available. However, it does not explicitly state when to use this tool over alternatives (e.g., for heart rate data specifically) nor when not to use it. With many sibling list tools, more explicit routing would be helpful, but the scope requirement gives some usage guidance.

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