Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio

get_publish_status_report

Retrieve paginated publish status reports with optional date range and filter parameters. Monitor app publishing success, failure, and other statuses.

Instructions

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

Retrieves paginated publish status 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 publish status. Allowed: 0=Success, 1=Failed, 2=Canceled, 3=Timeout, 90=Waiting, 91=Running, 92=Completing, 99=Unknown, 200=NotStarted, 201=Stopped, 202=InProgress, 203=AwaitingResponse

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

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

Filter by status (success only):
    get_publish_status_report(
        start_date="2024-01-01",
        end_date="2024-12-31",
        status=0
    )

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?

No annotations provided, so description carries full burden. Discloses pagination, default page size, date range behavior, status codes, and return envelope structure. Lacks mention of auth or rate limits, but adequate.

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?

Well-structured with distinct sections for purpose, args, returns, and examples. Each sentence adds value; no redundancy.

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?

Covers all parameters, return envelope, and includes examples. No missing essential details given the presence of output schema. Could mention sibling tools but not required for basic 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?

Schema has 0% description coverage; the description provides full parameter details including formats, defaults, allowed values (status codes), and examples, adding significant meaning beyond the schema alone.

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 states the tool retrieves a 'publish status report' with optional filtering. It does not explicitly differentiate from sibling get_* tools, but the resource name is specific enough.

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 explains when to use (retrieve report, filter) and behavior without filters, but does not guide against using it for other reports or mention alternatives among siblings.

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