Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio

get_signing_report

Get paginated signing report data with optional date range, organization, OS, and build status filters to analyze build signing history.

Instructions

Get signing report, optionally filtered by date range and other parameters.

Retrieves paginated signing report data. Called without start_date and end_date, returns every item in the report. Supports filtering by organization, OS, and build status.

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) organization_id: Filter by organization UUID os: Filter by OS ("ios" or "android") build_status: Filter by build status. Allowed: 0=Success, 1=Failed, 2=Canceled, 3=Timeout, 90=Waiting, 91=Running, 92=Completing, 99=Unknown

Returns: Standard envelope (see docs/tool_contract.md): - Success: success (true), data (list of signing report 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 signing report (no date filter): get_signing_report()

Get signing report for last month:
    get_signing_report(
        start_date="2024-11-01",
        end_date="2024-11-30"
    )

Filter by OS and build status:
    get_signing_report(
        start_date="2024-01-01",
        end_date="2024-12-31",
        os="ios",
        build_status=0
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNo
pageNo
sizeNo
end_dateNo
start_dateNo
build_statusNo
organization_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses pagination behavior (default size=50, use page), date range handling, filtering by organization/OS/build status, and references the return envelope. Examples illustrate behavior. No annotations exist, so burden is fully met.

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?

The description is well-structured with sections (general, important note, args, returns, examples), front-loaded with purpose, and every sentence adds value. No wasted text.

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 7 parameters, no required ones, and an output schema reference, the description covers all aspects: purpose, filters, pagination, return format, and examples. It is fully self-contained for agent decision-making.

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 compensates fully with a detailed 'Args:' section: includes format for dates, allowed values for os, build_status numeric mapping, and page/size defaults. This adds essential meaning beyond the 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 identifies the verb 'Get' and resource 'signing report', with 'optionally filtered by date range and other parameters' adding specificity. It distinguishes from sibling tools by focusing on the signing report aggregation.

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 explains when to call without filters ('returns every item') and lists supported filters, providing clear context. However, it does not explicitly mention when not to use or provide 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