Hevy MCP Pro

get_exercise_history

Retrieve per-set history for a specific exercise template across all workouts, with optional date filtering. This targeted approach avoids the overhead of paginating every workout.

Instructions

Fetch per-set history for a single exercise template across all workouts. Optionally bounded by startDate/endDate (ISO 8601). Much cheaper than paginating /v1/workouts when you only care about one exercise.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "templateId": "<templateId>"
    },
    "name": "get_exercise_history"
  }
}

Input Schema

Name	Required	Description	Default
`endDate`	No
`startDate`	No
`templateId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It adds useful behavioral context: per-set history, all workouts scope, optional date bounds, and a cost/performance hint. However, it does not disclose return format, ordering, or error behavior, leaving some transparency gaps.

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, front-loaded with the primary purpose and optional parameters, followed by a usage rationale. No filler or redundant repetition of schema details.

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?

For a read-only fetch with no output schema, the description covers the essential context: scope (single template, all workouts), optional date bounding, and performance rationale. It could be more complete by hinting at response contents, but 'per-set history' is reasonably descriptive. Lacks annotations, but the description is still solid.

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

Parameters4/5

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

Despite 0% schema coverage, the description meaningfully adds parameter context: templateId is tied to 'single exercise template', and startDate/endDate are described as optional and ISO 8601. This goes beyond the schema's raw patterns and helps the agent understand input semantics.

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 the tool fetches per-set history for a single exercise template across all workouts, which is specific and distinguishes it from siblings like list_workouts or get_exercise_progression. It also notes it is cheaper than paginating /v1/workouts, reinforcing its focused purpose.

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

Usage Guidelines4/5

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

The description explicitly says to use this when you only care about one exercise and provides an alternative (paginating /v1/workouts). It does not explicitly list when not to use it, but the 'when' condition and alternative are clear enough for most contexts.

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