Skip to content
GitmoapAPIBeta
Codetags
GET/repositories/{repo_id}/tags

List tags in a repository

list_tags
  • tag:read
    A token needs the tag:read scope: View tagsGranted by mcp_agent, mcp_agent_write, read_api, read_repository, write_api, write_repository.Every operation this scope unlocks
  • Single-resource

    x-gitmoap-isolation: {"kind":"single_or_self_scoped"}

  • Paginated
    Pass the next_token a page returns to get the next one.

The repository's tags in name order, ascending by default, optionally narrowed to names containing a search term (case-insensitive). Each comes with the commit it points to. Page with next_token, passed back unchanged, in either order; a sort other than the two listed, or a token this listing did not hand out, is refused.

Parameters

Path
  • repo_idRepositoryId (string · uuid)Repository ID
Query
  • limitinteger · int32optionalMaximum number of tags to return (1-100, default 20)
  • next_tokenstringoptionalPagination cursor
  • searchstringoptionalFilter tags by name substring
  • sortstringoptionalSort order: name_asc (default) or name_desc

Responses

200Tags listedapplication/json
  • itemsarray of RepositoryTag
    • The RepositoryTag schema
    • commitCommit
      • The Commit schema
      • author_emailEmail (string)
      • author_namestring
      • authored_atstring
      • commit_shaCommitHash (string)
      • committed_atstring
      • committer_emailEmail (string)
      • committer_namestring
      • repository_idRepositoryId (string · uuid)
      • short_shaShortCommitHash (string)
      • titlestring
      • author_avatar_urlstring or nulloptional
      • committer_avatar_urlstring or nulloptional
      • messagestring or nulloptional
      • parent_shasarray of CommitHash (string)optional
      • tagsarray of TagName (string)optional
    • repository_idRepositoryId (string · uuid)
    • tag_nameTagName (string)
    • tag_typeTagTypelightweightannotated
    • tag_messagestring or nulloptional
    • taggerTagger or nulloptional
  • next_tokenstring or nulloptional
200 exampleSynthesized example
{
"items": [
{
"commit": {
"author_email": "lin@acme.example",
"author_name": "Mara Okafor",
"authored_at": "2026-10-11T10:38:03Z",
"commit_sha": "fa418c922d568079cc9c5f5b3277aea20e619ac8",
"committed_at": "2026-10-16T08:50:49Z",
"committer_email": "tomas@acme.example",
"committer_name": "payments-api",
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"short_sha": "f07311f0eba6ed115cfe87943c30c3d70bbfe0fb",
"title": "Label every synthesized example"
},
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"tag_name": "payments-api",
"tag_type": "lightweight"
},
{
"commit": {
"author_email": "tomas@acme.example",
"author_name": "Mara Okafor",
"authored_at": "2026-10-16T06:07:20Z",
"commit_sha": "3e9d3d4706536e18d057ac7ed957ca6850bc30ad",
"committed_at": "2026-10-09T02:10:35Z",
"committer_email": "tomas@acme.example",
"committer_name": "payments-api",
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"short_sha": "9a4f2f7514eb7ef66fe32596d8abdccb62bbcc78",
"title": "Draw the region map from operation density"
},
"repository_id": "5b0e7c2a-9d14-4e8b-a6f1-2c3d4e5f6a70",
"tag_name": "payments-api",
"tag_type": "lightweight"
}
],
"next_token": "next-token-8766"
}
400An unknown sort, an unreadable pagination token, or a malformed repository IDapplication/json
Error codes
  • BAD_REQUESTThe request is malformed: a parameter or a body field is not a well-formed value of its type
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
400 exampleSynthesized example
{
"error": {
"code": "code-83d9",
"message": "Stream pipeline status into the run header"
}
}
401Unauthenticated — no credential, or an invalid oneapplication/json
Error codes
  • UNAUTHORIZEDNo credential was sent, or the one sent is invalid, expired or revoked
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
401 exampleSynthesized example
{
"error": {
"code": "code-8cdb",
"message": "Pin a page's payload to the build that rendered it"
}
}
403Forbidden — the caller's access level or token scope is insufficientapplication/json
Error codes
  • FORBIDDENYou are signed in but may not do this here; reason names the permission or the rule that refused it
  • INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs; required_scope names it
  • PERMISSION_REQUIREDYou need a permission you do not hold here; the message names it
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
403 exampleSynthesized example
{
"error": {
"code": "code-7247",
"message": "Inline scalar newtypes but keep their brand"
}
}
404Not found — or found and private, which is masked as absentapplication/json
Error codes
  • NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
404 exampleSynthesized example
{
"error": {
"code": "code-f838",
"message": "Draw the region map from operation density"
}
}

CLI

gitmoap tags list

  • --repo-ididRepository ID (id or owner/repo path)
  • --limitnumberoptionalMaximum number of tags to return (1-100, default 20)
  • --next-tokenstringoptionalPagination cursor
  • --searchstringoptionalFilter tags by name substring
  • --sortstringoptionalSort order: name_asc (default) or name_desc

Used in these guides