Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio

get_publish_resign_report

Retrieve publish resign reports with optional filters for date range, app name, organization, and status. Results are paginated to manage large datasets.

Instructions

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

Retrieves paginated publish resign data. Called without start_date and end_date, returns every item in the report. Supports filtering by app name, organization, and 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) app_name: Filter by app name organization_id: Filter by organization UUID status: Filter by resign status. Allowed: 0=waiting, 1=processing, 2=succeeded, 3=failed, 4=cancelled, 5=timeout

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

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

Filter by status (succeeded only):
    get_publish_resign_report(
        start_date="2024-01-01",
        end_date="2024-12-31",
        status=2
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
statusNo
app_nameNo
end_dateNo
start_dateNo
organization_idNo

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 must disclose behavioral traits. It does so by detailing pagination behavior, default page size, filter effects, and the response envelope structure. It does not mention any side effects or permissions, but as a read-only report retrieval, the transparency is adequate.

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 (intro, args, returns, examples) and uses clear language. It is somewhat verbose (e.g., repeated mention of pagination), but every sentence provides value. The structure aids readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (external), the description covers the key usage aspects: pagination, filtering, and response envelope. It includes examples for common cases (no filters, date range, status filter). It does not explain edge cases or behavior with invalid parameters, but overall it is sufficient for correct invocation.

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 description coverage is 0%, so the description carries the full burden. It provides clear descriptions for all 7 parameters, including format examples for dates, allowed integer values for status (with mapping), and pagination parameters (page, size). This adds significant meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as retrieving a publish resign report with optional filters. It states the resource ('publish resign report') and action ('get'). However, it does not explicitly distinguish this report from sibling report tools (e.g., get_build_history_report), leaving the agent to infer when to use this specific report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides guidance on parameter usage and pagination, including examples for different scenarios. However, it lacks explicit instructions on when to choose this tool over alternatives among the many sibling report tools. No 'when not to use' or prerequisite conditions are stated.

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