Skip to main content
Glama

eksisozluk_trending

Fetch the current trending topics on Ekşi Sözlük with pagination and a configurable result limit to see what users are discussing right now.

Instructions

Gündem — the trending topics on eksisozluk.com right now.

page: list page (50 topics per page). limit: 1..50 topics returned. Each topic: title, slug, topic_id, entry_count, url.

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": "eksisozluk_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden; "list" and "trending" imply a safe read, and it discloses pagination mechanics (50 topics per page, limit 1..50). It does not state whether authentication is needed, whether results are cached or time-sensitive, or what happens when page exceeds available pages.

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?

Three short lines, front-loaded with a one-line purpose followed by paging rules and the returned field list. Every sentence earns its place with no filler.

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?

An output schema exists, so return fields did not need repeating, yet the description still lists them for quick scanning. Parameters are fully explained; the only gaps are auth/rate-limit context for a very simple read-only list tool, which is a minor omission.

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?

Schema coverage is 0%, so the description must compensate, and it does: page is defined as a 50-topic list page and limit as a 1..50 count. It omits the default values (1 and 20) and any note about how page and limit interact, keeping it below a 5.

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?

"Gündem — the trending topics on eksisozluk.com right now" names a specific resource (trending topics) and a temporal scope (right now), which separates it from search_topics and get_topic. It stops short of explicitly contrasting with siblings such as eksisozluk_debe, so an agent must infer which list tool is the right one.

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?

Usage is only implied via "right now" — the agent can guess this is for browsing currently popular topics rather than searching or reading a specific topic. There is no explicit statement of when to prefer this over eksisozluk_debe or eksisozluk_channel_topics, and no exclusions or prerequisites.

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