Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio

get_commits_by_branch

Retrieve paginated commits for a build branch, providing commit hash, message, author, and build details.

Instructions

Get commits for a build branch (paginated).

Returns a list of commits for the given branch ID, including commit hash, message, author, commit date, tags, and associated builds. When page and size are provided, the API returns pagination metadata (page, perPage, pageCount, totalCount, enablePrevious, enableNext) which is included in meta.

Args: branch_id: The branch ID (e.g. UUID). page: Page number (1-based). If provided with size, enables pagination and returns pagination metadata in meta. Default when using pagination: 1. size: Page size. If provided with page, enables pagination. Default when using pagination: 25. Values above 100 are capped at 100.

Returns: Standard envelope (see docs/tool_contract.md): - Success: success (true), data (list of commit objects with id, hash, message, author, email, commitDate, tags, builds, etc.), meta (when pagination used: page, page_size, page_count, total_count, enable_previous, enable_next; otherwise empty or minimal). - Error: success (false), error (tool, type, message, details).

Examples: Get commits (no pagination): get_commits_by_branch(branch_id="branch-uuid") Get first page of commits: get_commits_by_branch(branch_id="branch-uuid", page=1, size=25) Get page 2 with 10 items: get_commits_by_branch(branch_id="branch-uuid", page=2, size=10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
branch_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: pagination metadata in meta, default values, value cap at 100, standard return envelope format. No contradictions.

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?

Well-structured with summary, Args, Returns, and Examples sections. Comprehensive but slightly lengthy; could be trimmed slightly while retaining all information.

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?

Complete for a paginated list tool with output schema. Covers all parameters, return format, and examples. No gaps for agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond bare schema: branch_id as UUID, page as 1-based with default and pagination behavior, size with default and cap. Schema coverage was 0%, so description compensates fully.

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?

Clearly states 'Get commits for a build branch' and specifies return fields (hash, message, author, etc.). Distinguishes from sibling tools like get_commit_details which likely returns a single commit.

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?

Provides detailed usage context: pagination is enabled when both page and size are provided, default values, and value caps. Includes examples. However, it does not explicitly mention when to use this tool over alternatives like get_commit_details.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/appcircleio/appcircle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server