Skip to main content
Glama

top_assets

Read-onlyIdempotent

This endpoint lists top streamed assets in a video collection

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_at": "<start_at>",
      "end_at": "<end_at>"
    },
    "name": "top_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number of the response.1
end_atYesDate in yyyy-MM-dd format
start_atYesDate in yyyy-MM-dd format
page_sizeNoAssets to list per page.1000
workspace_idNoGumlet video workspace ID. Preferred. Provide `workspace_id`, or deprecated `collection_id` / `source_id` (same ID).
collection_idNoDeprecated. Use `workspace_id` instead. Still accepted for backwards compatibility.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / collection_id / description
      Previous value: -"Gumlet workspace ID"New value: +"Deprecated. Use `workspace_id` instead. Still accepted for backwards compatibility."
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Gumlet video workspace ID. Preferred. Provide `workspace_id`, or deprecated `collection_id` / `source_id` (same ID).",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / end_at / description
      Previous value: -"Date string in \"yyyy-mm-dd\" format"New value: +"Date in yyyy-MM-dd format"
    • addedInput schema / properties / end_at / format
      Added value: +"date"
    • changedInput schema / properties / start_at / description
      Previous value: -"Date string in \"yyyy-mm-dd\" format"New value: +"Date in yyyy-MM-dd format"
    • addedInput schema / properties / start_at / format
      Added value: +"date"
  3. 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 a safe, idempotent, closed read, so the description should add what they cannot. It adds nothing about how "top" is computed, whether results are ordered, how workspace scoping behaves, or the large default page size of 1000 — meaningful traits for an analytics read.

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?

A single front-loaded sentence with no filler, so it is concise. The problem is under-specification rather than verbosity: the one sentence spends its words on a vague qualifier ("top streamed") instead of the ranking criteria or required inputs.

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 shape need not be explained. However, for a ranked-analytics tool with six parameters, two of them required, the description omits the ranking definition, the mandatory date range, and pagination defaults — gaps an agent must guess at to call it correctly.

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 baseline is 3; the schema already documents start_at, end_at, page, page_size, workspace_id, and the deprecated collection_id. The description adds no meaning beyond that, notably omitting that both dates are required.

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 gives a verb and resource ("lists top streamed assets") and hints at scope ("in a video collection"), which separates it loosely from plain list_assets. But "top" is left undefined — no ranking metric, no tie-breaking, no period — so an agent cannot tell precisely what the result set represents.

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?

No guidance on when to use this instead of analytics_aggregated_data, asset_analytics, retrieve_analytics, or list_assets, all of which compete for similar questions. It also never says a date range is mandatory, which is the main precondition imposed by the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources