Skip to main content
Glama

Gumlet MCP

by com.gumlet.mcp
OverviewDiscussionsAdmin

insights_aggregated_data

Read-onlyIdempotent

This endpoint retrieves aggregated data of the given metrics.

Input Schema

NameRequiredDescriptionDefault
filtersNoGet aggregations for metrics with multiple filters, `value` should be an exact match
aggregateNoAggregate multiple metrics at the same time
timeframeNoThe timeframe to get the data for. The maximum range between start_at and end_at is 60 days.
workspace_idNoThe unique identifier of the Gumlet workspace ID available on the Video Workspaces.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / timeframe / description
      Previous value: -"The timeframe to get the data for. Currently we only support maximum difference between `start_at` and `end_at` to be *60 days*"New value: +"The timeframe to get the data for. The maximum range between start_at and end_at is 60 days."
    • changedInput schema / properties / timeframe / properties / end_at / description
      Previous value: -"Use <b>yyyy-MM-dd</b> format"New value: +"Date in yyyy-MM-dd format"
    • changedInput schema / properties / timeframe / properties / start_at / description
      Previous value: -"Use <b>yyyy-MM-dd</b> format"New value: +"Date in yyyy-MM-dd format"
    • addedInput schema / properties / timeframe / required
      Added value: +[
+  "start_at",
+  "end_at"
+]
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context of its own (no pagination, result size limits, or scoping notes), so it contributes little beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded sentence with zero waste, but it is so sparse that it leaves obvious questions unanswered. Brevity here reflects under-specification rather than helpful concision.

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

Completeness2/5

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

An output schema exists so return values need not be described, and the schema itself is well documented. However, for a tool with four nested, enum-heavy parameters and numerous confusingly similar siblings, the total absence of usage or differentiation context leaves the agent unable to confidently select it.

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

Parameters3/5

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

Schema description coverage is 100%, so the nested filters, aggregate, timeframe, and workspace_id parameters are already well documented in the schema. The description adds no parameter semantics beyond that, so the baseline 3 applies.

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

Purpose3/5

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

The description states a verb (retrieves) and a resource (aggregated data for given metrics), so the basic purpose is discernible. However, 'aggregated data of the given metrics' is vague and gives no basis for distinguishing it from near-identical siblings like analytics_aggregated_data or insights_breakdown_data.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many competing analytics/insights siblings. Nothing indicates context, prerequisites, or which family (insights vs analytics) applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gumlet MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources