Wakatime

Commits

commits

Read-onlyIdempotent

List the commits WakaTime has recorded for one project belonging to a WakaTime user, given user_id (or "current") and the project name, with optional author, branch, and page. Returns each commit hash, message, author, branch, timestamps, and the coding time WakaTime attributes to it. Answers what has been committed to a project tracked by WakaTime and how much editor time went into it. Requires your own WakaTime personal OAuth token as _apiKey.

Input Schema

Name	Required	Description
`page`	No
`author`	No
`branch`	No
`_apiKey`	No	Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
`project`	Yes
`user_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.",
+  "type": "string"
+}

First observedMay 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so safety is covered. The description adds genuinely new context: it discloses the return shape (hash, message, author, branch, timestamps, attributed coding time) and, importantly, the auth requirement that a WakaTime personal OAuth token be passed as _apiKey. Pagination limits are not described.

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?

Four sentences, front-loaded with the purpose and followed by return shape, use case, and auth requirement, with no filler. Slight overlap between the return-value sentence and the use-case sentence keeps it from being maximally tight.

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?

An output schema exists, yet the description still summarizes return fields helpfully, and it covers auth, required keys, and optional filters for a 6-parameter tool. Only pagination behavior and how the project must be named/matched are left underspecified.

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?

Schema description coverage is only 17%, so the description must carry parameter meaning, and it largely does: it explains that user_id accepts an ID or the literal "current", that project is the project name, and that author, branch, and page are optional filters. Page is only labeled as optional without any pagination semantics, which is the remaining gap.

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?

Specific verb + resource ("List the commits WakaTime has recorded") scoped precisely to one project of one user, and it names the retrieval keys. It is clearly distinguishable from sibling tools like durations, heartbeats, and projects, which cover different resources within the same WakaTime domain.

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?

"Answers what has been committed to a project tracked by WakaTime and how much editor time went into it" gives a clear use case and signals when this tool applies. It stops short of naming alternatives (e.g. durations or stats for time-only questions) or stating when not to use it.

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

All Wakatime tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.