Skip to main content
Glama

Bestsellers

tg_bestsellers
Read-onlyIdempotent

Browse trending Persian ebooks and audiobooks overall or by category without sales figures. Returns paginated bestselling rankings to help you find currently popular titles.

Instructions

Hottest books now (trending ranking, no sales numbers), overall or per category.

For a keyword use tg_search(sort='bestselling').

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

Input Schema

NameRequiredDescriptionDefault
cursorNoPrevious next_cursor.
formatNoany
categoryNoCategory id (e.g. 68) or slug from tg_categories; empty = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuine data-content context ('trending ranking, no sales numbers'), which warns the agent that sales figures are absent and implies result ordering by trend. It says nothing about pagination behavior or result richness.

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?

Two short sentences with the scope and the data caveat front-loaded, followed by the alternative routing. Nothing is wasted and there is no ambiguity.

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?

For a simple read-only listing tool with three optional parameters and rich annotations, the description covers purpose, scope, and the main alternative. With no output schema, it still sketches the return content (trending books, no sales numbers), leaving only pagination mechanics and result fields implicit.

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 coverage is 67%, so most parameters are already documented in the schema itself, including cursor semantics and the category-to-slug mapping. The description only reinforces the category parameter ('overall or per category'), adding no detail about format or cursor usage beyond the schema, so baseline 3 applies.

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?

States a specific resource (books) and scope (hottest now, trending ranking, overall or per category), and explicitly names the sibling to use for keyword searches. An agent can distinguish this from tg_search without opening either schema.

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

Usage Guidelines4/5

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

Gives an explicit routing rule: for a keyword, use tg_search(sort='bestselling'). It also implies the browse-without-a-query case ('overall or per category'), but offers no exclusion or guidance relative to other browsing siblings such as tg_new_releases or tg_categories.

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