MCP Tools Reference: developerconnect.googleapis.com

Tool: fetch-repo-commit

Fetch details of a specific commit from a Git repository. To retrieve line-by-line patch hunks in FULL view, pass path_filters (for example, ['**'] for all files).

The following code sample shows how to use curl to call the fetch-repo-commit MCP tool.

Curl Request 
curl --location 'https://developerconnect.googleapis.com/mcp' \
--header 'content-type: application/json' \
--header 'accept: application/json, text/event-stream' \
--data '{
  "method": "tools/call",
  "params": {
    "name": "fetch-repo-commit",
    "arguments": {
      // Provide these details according to the MCP tool specification.
    }
  },
  "jsonrpc": "2.0",
  "id": 1
}'

Input Schema

Request message for FetchGitRepositoryLinkCommit.

FetchGitRepositoryLinkCommitRequest

JSON representation 
{
  "name": string,
  "commitSha": string,
  "view": enum (CommitView),
  "pathFilters": [
    string
  ]
}
Fields
name

string

Required. The resource name of the GitRepositoryLink in the format projects/*/locations/*/connections/*/gitRepositoryLinks/*.
commitSha

string

Required. The commit SHA, or symbolic revision (for example, branch name, tag, or Git reference).
view

enum (CommitView)

Optional. The level of commit details to return in the response. Defaults to FULL if unspecified. In FULL view, files metadata (paths and statuses) are returned; path_filters must also be specified to populate line patch hunks.
pathFilters[]

string

Optional. Path patterns or exact paths to filter returned files (only applicable in FULL view). When path_filters is specified, FileDiff.patch is populated for all matching files (use ["**"] to include patches for all changed files). When path_filters is omitted or empty, the full list of FileDiff is returned without patch diffs (FileDiff.patch is empty).

CommitView

The level of commit details to return in the response.

Enums
COMMIT_VIEW_UNSPECIFIED Unspecified, defaults to BASIC.
BASIC Basic view, returns commit metadata but no file diffs.
FULL Full view, returns commit metadata and file diffs.

Output Schema

Response message for FetchGitRepositoryLinkCommit.

FetchGitRepositoryLinkCommitResponse

JSON representation 
{
  "commit": {
    object (SCMCommit)
  },
  "files": [
    {
      object (FileDiff)
    }
  ]
}
Fields
commit

object (SCMCommit)

The commit metadata.
files[]

object (FileDiff)

List of file changes and patch diffs. Omitted when view is BASIC. Patch diffs (FileDiff.patch) are only populated when path_filters is specified in the request.

SCMCommit

JSON representation 
{
  "sha": string,
  "message": string,
  "author": string,
  "authorEmail": string,
  "commitTime": string,
  "url": string
}
Fields
sha

string

Full 40-character SCM commit SHA.
message

string

Commit message text.
author

string

The author's display name.
authorEmail

string

The author's email address.
commitTime

string (Timestamp format)

Timestamp when the commit was authored.

Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: "2014-10-02T15:01:23Z", "2014-10-02T15:01:23.045123456Z" or "2014-10-02T15:01:23+05:30".
url

string

The SCM provider's HTML URL link for this commit.

Timestamp

JSON representation 
{
  "seconds": string,
  "nanos": integer
}
Fields
seconds

string (int64 format)

Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be between -62135596800 and 253402300799 inclusive (which corresponds to 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z).
nanos

integer

Non-negative fractions of a second at nanosecond resolution. This field is the nanosecond portion of the duration, not an alternative to seconds. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be between 0 and 999,999,999 inclusive.

FileDiff

JSON representation 
{
  "path": string,
  "status": string,
  "patch": string
}
Fields
path

string

Relative path to the file in the repository.
status

string

Status of change: "ADDED", "MODIFIED", "REMOVED", "RENAMED".
patch

string

Standard unified diff patch hunk for the file. Only populated when path_filters is specified in the request; otherwise empty.

Tool Annotations

Tool annotations are sent to MCP clients to describe the basic risk of a given tool. Most clients treat these hints as untrusted, but they can be used to decide when a confirmation prompt might be sent to a user.

Along with the title string, the following boolean hints are defined as follows:

  • readOnlyHint: If true, the tool doesn't modify its environment. Default: false.
  • destructiveHint: If true, then the tool can perform destructive actions. If false, then the tool can only perform additive actions. Default: true.
  • idempotentHint: If true, then calling the tool repeatedly with the same arguments will have no additional effect on its environment. Default: false.
  • openWorldHint: If true, then the tool can interact with an 'open world' of external entities. If false, then the tool can only interact with internal entities. For example, a web search tool would be open world, while a memory tool would not be open world.

Destructive Hint: ❌ | Idempotent Hint: ✅ | Read Only Hint: ✅ | Open World Hint: ❌