get_v1_git_repos_name_commits
Walks a ref's history newest first, or one path's history when a path is given.
Walks a ref's history newest first, or one path's history when a
path is given. There is no cursor: the page is the newest limit commits.
| Tool | get_v1_git_repos_name_commits |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | GET /v1/git/repos/{name}/commits |
| Product | git |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
limit | integer | — | — | Limit caps the page. Anything not positive means 50; the cap is 100. |
name | string | — | — | Name is the repo to read, from the :name path segment. |
path | string | — | — | Path narrows the history to commits touching it; empty walks the whole ref. |
ref | string | — | — | Ref is the branch, tag or commit to walk back from; empty means HEAD. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_git_repos_name_commits",
"arguments": {
"limit": 0,
"name": "<name>",
"path": "<path>",
"ref": "<ref>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_get_v1_git_repos_name_commits | GET /v1/git/repos/{name}/commits | git | Walks a ref's history newest first, or one path's history when a path is given. |
The same capability over plain HTTP is in the git API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?