Skip to main content
Glama

list_analytics_capabilities

Explore available analytics features, including 7 functions, 60+ report types, dimensions, and time intervals to understand system reporting capabilities.

Instructions

Discover ALL analytics capabilities of this system. USE WHEN: User asks 'what analytics can you do?', exploring available reports, understanding metrics options, learning about analytics features. RETURNS: Complete list of 7 analytics functions with descriptions, 60+ report types, available dimensions, time intervals. EXAMPLE: Always run this when user first asks about analytics. No parameters needed - just call it!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function that returns a static JSON document listing all available analytics functions, report types, dimensions, intervals, and other capabilities. No actual API call; purely informational for tool discovery.
    async def list_analytics_capabilities(manager: KalturaClientManager) -> str:
        """
        List all available analytics capabilities and their use cases.
    
        This helper function provides a comprehensive overview of all analytics
        functions, making it easy for LLMs and developers to discover capabilities.
    
        Returns:
            JSON with detailed capability descriptions and examples
        """
        capabilities = {
            "analytics_functions": [
                {
                    "function": "get_analytics",
                    "purpose": "Comprehensive reporting and analysis",
                    "use_cases": [
                        "Performance metrics and rankings",
                        "Detailed breakdowns by category/user/time",
                        "Comparative analysis across content",
                        "Export-ready tabular data",
                    ],
                    "example": "get_analytics(manager, from_date, to_date, report_type='content')",
                },
                {
                    "function": "get_analytics_timeseries",
                    "purpose": "Time-series data for visualization",
                    "use_cases": [
                        "Creating charts and graphs",
                        "Trend analysis over time",
                        "Dashboard visualizations",
                        "Growth tracking",
                    ],
                    "example": "get_analytics_timeseries(manager, from_date, to_date, interval='days')",
                },
                {
                    "function": "get_video_retention",
                    "purpose": "Detailed viewer retention analysis",
                    "use_cases": [
                        "Finding where viewers drop off",
                        "Identifying replay segments",
                        "Optimizing content structure",
                        "Comparing audience segments",
                    ],
                    "example": "get_video_retention(manager, entry_id='1_abc')",
                },
                {
                    "function": "get_realtime_metrics",
                    "purpose": "Live analytics data",
                    "use_cases": [
                        "Monitoring live events",
                        "Real-time dashboards",
                        "Immediate campaign feedback",
                        "Issue detection",
                    ],
                    "example": "get_realtime_metrics(manager, report_type='viewers')",
                },
                {
                    "function": "get_quality_metrics",
                    "purpose": "Streaming quality analysis",
                    "use_cases": [
                        "QoE monitoring",
                        "Playback issue detection",
                        "Infrastructure optimization",
                        "User experience tracking",
                    ],
                    "example": "get_quality_metrics(manager, from_date, to_date)",
                },
                {
                    "function": "get_geographic_breakdown",
                    "purpose": "Location-based analytics",
                    "use_cases": [
                        "Global reach analysis",
                        "Regional content strategy",
                        "Market penetration",
                        "CDN optimization",
                    ],
                    "example": "get_geographic_breakdown(manager, from_date, to_date, granularity='country')",
                },
            ],
            "report_types": list(REPORT_TYPE_MAP.keys()),
            "available_dimensions": [
                "device",
                "country",
                "region",
                "city",
                "domain",
                "entry_id",
                "user_id",
                "application",
                "category",
            ],
            "time_intervals": ["hours", "days", "weeks", "months", "years"],
            "user_filters": ["all", "anonymous", "registered", "specific_user", "cohort"],
            "quality_metrics": ["overview", "experience", "engagement", "stream", "errors"],
            "geographic_levels": ["world", "country", "region", "city"],
        }
    
        return json.dumps(capabilities, indent=2)
  • Tool schema definition in list_tools(), specifying name, detailed description, and empty input schema (no parameters required).
    types.Tool(
        name="list_analytics_capabilities",
        description="Discover ALL analytics capabilities of this system. USE WHEN: User asks 'what analytics can you do?', exploring available reports, understanding metrics options, learning about analytics features. RETURNS: Complete list of 7 analytics functions with descriptions, 60+ report types, available dimensions, time intervals. EXAMPLE: Always run this when user first asks about analytics. No parameters needed - just call it!",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Dispatch logic in call_tool() that routes requests for this tool to the handler function.
    elif name == "list_analytics_capabilities":
        result = await list_analytics_capabilities(kaltura_manager, **arguments)
  • Import of the tool handler into server.py.
    list_analytics_capabilities,
  • Export of the tool from tools/__init__.py to make it available for import.
    list_analytics_capabilities,
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses behavioral traits: returns a complete list with details (7 functions, 60+ reports, dimensions, intervals), and states no parameters needed. However, it lacks info on rate limits, auth needs, or error handling, leaving some gaps.

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?

Front-loaded with purpose, followed by usage guidelines, returns, and example. Sentences are efficient, but could be slightly more streamlined (e.g., combining some usage examples). Overall, minimal waste and well-structured.

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 0 parameters, no annotations, and no output schema, the description provides good context: purpose, usage, return details, and example. However, it doesn't specify output format or error cases, leaving some completeness gaps for a tool with no structured output info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema coverage, the baseline is 4. The description adds value by explicitly stating 'No parameters needed - just call it!', clarifying that no inputs are required beyond what the empty schema indicates.

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 states the verb 'Discover' and resource 'ALL analytics capabilities', specifying the scope comprehensively. It distinguishes from siblings like get_analytics (which likely retrieves specific data) by focusing on listing available capabilities rather than fetching analytics data.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use scenarios: 'User asks what analytics can you do?', exploring reports, understanding metrics, learning features. It includes an example: 'Always run this when user first asks about analytics', offering clear guidance on context and 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/zoharbabin/kaltura-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server