Skip to main content
Glama
appcircleio

appcircle-mcp

Official
by appcircleio
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_distribution_app_version_report

Retrieve daily usage reports for distributed app versions, with optional date range, profile, and OS filters. Results are paginated for manageable data access.

Instructions

Get daily usage report for distributed app versions.

Retrieves paginated daily usage data for app versions distributed 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 app version report (no date filter): get_distribution_app_version_report()

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

Filter by profile and OS:
    get_distribution_app_version_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

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Describes pagination behavior, default page size, token limit concerns, and return format (standard envelope). Does not mention any destructive actions or side effects, which is appropriate for a read-only report tool. Some additional details like date format examples enhance transparency.

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?

Well-structured with summary, details, args, returns, and examples. Every section adds value. A bit verbose, but clarity outweighs conciseness. Could potentially shorten the examples, but overall efficient.

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, pagination, and multiple filters, the description covers all necessary aspects: default behavior, pagination mechanics, parameter details, return format reference. Existence of an output schema (standard envelope) means return values are handled separately. Agent has full context 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 has 0% description coverage, so description must compensate. It includes an 'Args:' section with descriptions, types, formats, defaults, and examples for all 7 parameters. This adds substantial meaning beyond schema, such as date format, default page size, and filter semantics.

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?

Starts with a clear verb+resource: 'Get daily usage report for distributed app versions.' The description further specifies it retrieves paginated daily usage data, making the purpose unambiguous. It does not explicitly distinguish from siblings, but the resource is unique enough among sibling tools.

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?

Provides usage context: behavior without start/end dates returns all items, supports filtering by profile, OS, organization. However, it lacks explicit when-to-use vs. alternatives or when-not-to-use. The sibling list contains many 'get_*' tools, but no clear differentiation is 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