Withings MCP

Withings Body Measures

withings_list_body_measures

Read-onlyIdempotent

Fetch weight and body composition measurements from Withings for a date range. Enables AI agents to access punctual body metrics for analysis.

Instructions

List Withings punctual measurements such as weight and body composition. 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"
+}
```

Changed6 schema fields changedv0.4.11Jul 30, 2026

changedInput schema / properties / after / description

Previous value: -"Only return Withings records after this time. Converted to Withings startdate."New value: +"Inclusive start bound. Converted to Withings startdate (epoch) or startdateymd (YYYY-MM-DD) per action."

removedInput schema / properties / after / format
```
Removed value: -"date-time"
```

changedInput schema / properties / after / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^\\d{4}-\\d{2}-\\d{2}([Tt ]\\d{2}:\\d{2}(:\\d{2})?(\\.\\d+)?([Zz]|[+-]\\d{2}:?\\d{2})?)?$"

changedInput schema / properties / before / description

Previous value: -"Only return Withings records before this time. Converted to Withings enddate."New value: +"Inclusive end bound. Converted to Withings enddate (epoch) or enddateymd (YYYY-MM-DD) per action."

removedInput schema / properties / before / format
```
Removed value: -"date-time"
```

changedInput schema / properties / before / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^\\d{4}-\\d{2}-\\d{2}([Tt ]\\d{2}:\\d{2}(:\\d{2})?(\\.\\d+)?([Zz]|[+-]\\d{2}:?\\d{2})?)?$"

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.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds the scope requirement and a safety disclaimer, which is useful context beyond annotations. However, it does not mention pagination behavior, privacy_mode handling, or return format, though these are partially covered by the schema. Given the annotation coverage, a 3 is appropriate.

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 with no fluff. The core purpose is front-loaded, followed by two essential caveats. Every word earns its place.

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 rich schema (8 parameters, all described, output schema present) and strong annotations, the description is sufficient for an agent to understand the tool's purpose and call it correctly. It misses a bit of detail on output format or privacy, but those are in the schema. Overall, it's complete enough for the tool's complexity.

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%, so most parameters are already described. The description itself adds no parameter-specific details beyond what the schema provides. Baseline 3 is correct because the schema does the heavy lifting.

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'), a specific resource ('Withings punctual measurements'), and gives concrete examples ('weight and body composition'). This clearly distinguishes it from sibling tools like withings_list_activity or withings_list_sleep.

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 only mentions a prerequisite (requires user.metrics scope) and a disclaimer (not medical advice), but gives no guidance on when to choose this tool over alternatives. It does not explicitly mention sibling tools or conditions for preferring one over another.

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