Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio

get_build_history_report

Retrieve a paginated build history report with optional filters (date range, build profile, organization) for monitoring and analysis.

Instructions

Get build history report, optionally filtered by date range.

Retrieves paginated build history with build metadata, artifacts, duration, status, and optional filters by date range, build profile and organization. Called without start_date and end_date, returns every item in the report.

IMPORTANT: Results are paginated by default to prevent token limit issues. Default page size is 50 items. Use page parameter to retrieve additional results.

Args: start_date: Optional start date (format: "YYYY-MM-DD", e.g., "2024-01-01") end_date: Optional end date (format: "YYYY-MM-DD", e.g., "2024-12-31") page: Page number (starts from 1, default: 1) size: Items per page (1-100, default: 50) build_profile_name: Filter by build profile name organization_id: Filter by organization UUID

Returns: Standard envelope (see docs/tool_contract.md): - Success: success (true), data (list of build history records), meta (count, page, page_size, total_count, total_pages, has_more, next_page, filters). - Error: success (false), error (tool, type, message, details).

Examples: Get all build history (no date filter): get_build_history_report()

Get build history for last month:
    get_build_history_report(
        start_date="2024-11-01",
        end_date="2024-11-30"
    )

Filter by build profile:
    get_build_history_report(
        start_date="2024-01-01",
        end_date="2024-12-31",
        build_profile_name="RN076iOS"
    )

Get second page with custom size:
    get_build_history_report(
        start_date="2024-01-01",
        end_date="2024-12-31",
        page=2,
        size=25
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
end_dateNo
start_dateNo
organization_idNo
build_profile_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully discloses behavioral traits: pagination (default page size 50), the effect of omitting date filters, and the reason for pagination (token limit issues). It does not mention rate limits or security, but these are not critical for this read operation.

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?

The description is well-structured with sections for overview, important notes, args, returns, and examples. It is detailed but not overly verbose; every sentence is informative. Slightly lengthy but justified by the number of parameters.

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?

Given the 6 optional parameters and the existence of an output schema, the description is comprehensive. It covers all parameter details, behavior, pagination, return structure, and provides multiple examples. It is complete enough for an AI agent to invoke correctly.

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?

Schema coverage is 0%, but the description thoroughly explains each parameter's purpose, format (date format 'YYYY-MM-DD'), constraints (page starts at 1, size 1-100, defaults), and provides examples. This adds significant value beyond the bare schema.

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?

The description clearly states the tool's action ('Get build history report'), the resource ('build history'), and its optional filtering by date range. It distinguishes itself from sibling tools that focus on other entities like bundle identifiers or build profiles.

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?

The description provides clear context on when to use the tool (retrieving build history) and explains default behavior (returns all items without date filters). It also warns about pagination to avoid token limits. However, it does not explicitly mention when not to use it or compare to alternatives.

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