Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_get_zen_top_channels

Retrieve top Zen channels ranked by views. Sort and paginate results to analyze channel performance.

Instructions

Дзен - Рейтинг по просмотрам Дзен каналов Method: GET Path: /zen/top/channels Пример запроса https://api.keys.so/zen/top/channels?sort=viewsRank%7Casc&page=1&per_page=25

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keyso_get_zen_top_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoin: query | Порядковый номер страницы результатов
sortNoin: query | Сортировка данных по полям.<br><br>Формат: `field|direction`, где<br><br>`field` - имя колонки<br>`direction` - направление сортировки, asc - по возрастанию, desc - по убыванию<br><br>Например: `pos|asc`, либо по двум полям `pos|asc,wsk|desc`
tokenNoAPI token override (fallback: KEYSO_TOKEN env)
base_urlNoOverride API base URL
per_pageNoin: query | Количество результатов на одной странице

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden and does provide some context: it specifies GET (implying a read-only operation) and that the data is a views-based rating of channels. However, it does not mention authentication expectations, rate limits, or the shape/content of the returned ranking, so the behavioral disclosure is adequate but thin.

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

Conciseness5/5

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

The description is compact and front-loaded: purpose, method, path, and a concrete example in three short lines. There is no filler or redundant restating of the tool name beyond the natural Russian title.

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

Completeness3/5

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

The method, path, and example query give enough to make a basic call, and the schema covers parameter details. But there is no output schema and the description does not describe the response format, default pagination behavior, or authentication context, so completeness is only average.

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?

The schema already documents all five parameters, so the baseline is satisfied. The example URL adds real value by showing an endpoint-specific sort field (`viewsRank`), the `field|direction` encoding, and pagination parameters, which helps an agent construct a valid request.

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

Purpose4/5

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

The description identifies the resource (top Zen channels) and the ranking criterion (by views), so an agent can infer it returns a ranked list of Zen channels. It does not explicitly differentiate this from the sibling Zen dashboard/publication tools, relying mostly on the tool name and path.

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 is provided about when to use this tool versus related Zen endpoints such as keyso_get_zen_dashboard, keyso_get_zen_channel_publications, or keyso_get_zen_channel_new_top_publications. The description only shows the endpoint and an example, leaving selection to the agent's inference.

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

Deploy Server

Other Tools