Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio

get_distribution_sent_report

Retrieve daily usage reports for distributed app sharing. Filter by date, profile, OS, or organization with paginated results.

Instructions

Get daily usage report for distributed app sharing.

Retrieves paginated daily usage data for app sharing (distribute-sent) via distribution profiles. Called without start_date and end_date, returns every item in the report. Supports filtering by profile, OS, and organization.

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) profile_name: Filter by distribution profile name os: Filter by OS ("ios" or "android") organization_id: Filter by organization UUID

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

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

Filter by profile and OS:
    get_distribution_sent_report(
        start_date="2024-01-01",
        end_date="2024-12-31",
        profile_name="Internal Testing",
        os="ios"
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNo
pageNo
sizeNo
end_dateNo
start_dateNo
profile_nameNo
organization_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Since no annotations are provided, the description carries full burden. It discloses that results are paginated by default with a default size of 50, and explains how to navigate pagination. It also specifies the return envelope structure. This is thorough for a read-only report retrieval tool.

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 a brief intro, an Args section, a Returns section, and Examples. It is slightly long but every section adds value. The most important information (purpose and pagination) is front-loaded.

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 tool has 7 parameters, no annotations, and an output schema exists, the description covers all necessary aspects: purpose, all parameters with formats and defaults, pagination behavior, return structure, and usage examples. It is fully complete for effective tool selection and 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?

With 0% schema coverage, the description adds extensive meaning: it provides formats, examples, defaults, and explanations for all 7 parameters. It clarifies that start_date/end_date are optional and how they affect results, and explains filtering options like profile_name, os, and organization_id.

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 explicitly states it retrieves a 'daily usage report for distributed app sharing', with a clear verb ('Get') and resource ('daily usage report'). It distinguishes itself from sibling tools like get_build_history_report by focusing on app sharing distribution data.

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 use the tool (to get paginated daily usage data) and provides multiple examples showing different call patterns. It does not explicitly state when not to use it or mention alternatives, but the examples and parameter descriptions give clear guidance.

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