Skip to main content
Glama

get_recent_commits

Read-only

List recent commits of one repository with SHA, author, date, and message, optionally filtering by days, author, or branch to answer what changed or who committed.

Instructions

List the most recent commits of ONE repository: SHA, author, date and message, optionally filtered by days back, author login, or branch. Use for 'what changed', 'who committed', 'last commit', or activity in the last N days. Do NOT use for repository metadata such as stars or language (use get_repository) or for pull requests (use list_pull_requests).

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": {
      "repo": "<repo>"
    },
    "name": "get_recent_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository as 'owner/name' (e.g. 'octocat/hello-world'). A bare name like 'hello-world' is resolved against the authenticated user's account.
limitNoMaximum number of items to return (1-50). Totals are reported separately, so a small limit is fine when only a count is needed.
authorNoOnly commits by this GitHub login or email.
branchNoBranch or tag name. Omit for the default branch.
since_daysNoOnly commits from the last N days (1-365). Omit for the latest commits regardless of age.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and the description adds that results are scoped to a single repository and are ordered by recency with optional narrowing filters. It does not discuss pagination behaviour or whether totals are returned alongside the list, which is the main remaining gap. Given annotation coverage, a 4 is fair.

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?

Three short sentences, front-loaded with what is returned and scoped, then use cases, then exclusions. No filler and no repetition of the tool name.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating the returned fields (SHA, author, date, message). With five fully documented parameters and annotations carrying the safety profile, an agent has everything needed to select and invoke the tool correctly.

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 coverage is 100%, so every parameter including repo format ('owner/name' with bare-name resolution), limit range, and since_days range is already documented in the schema. The description's phrase 'optionally filtered by days back, author login, or branch' merely restates those parameters without adding syntax, defaults, or interaction rules. Baseline 3 applies when 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?

States a specific verb and resource ('List the most recent commits') and adds the returned fields (SHA, author, date, message) plus the 'ONE repository' scope. It explicitly names the two siblings it must not be confused with (get_repository, list_pull_requests), so an agent can separate it from alternatives without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete use cases ('what changed', 'who committed', 'last commit', activity in the last N days) and an explicit when-not clause with the correct substitute tool for each exclusion. This is the full when/when-not/alternatives pattern rather than implied guidance.

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