Skip to main content
Glama

List Trends Bookmarks

list_trends_bookmarks
Read-onlyIdempotent

[read] The caller's saved trend searches (bookmarks) of one list. kind is the page the search came from: news, gservice-trends, gservice-maps, twitter-trends, tt-trends, yt-trends, ig-trends, rd-trends-search, rd-trends-subreddit or tg-finder (the Telegram channel finder: query). A bookmark keeps only the search parameters (trends_bookmark_params), never the result: run it again with the matching list/search tool.

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": {
      "kind": "<kind>"
    },
    "name": "list_trends_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds the non-obvious fact that a bookmark persists only `trends_bookmark_params` and never the result set — genuinely useful behavioral context. It leaves out pagination and the returned record shape, so not a 5.

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

Conciseness4/5

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

Front-loaded with the '[read]' marker and the core statement, then the value list. The long `kind` enumeration is bulky but every entry is load-bearing given the 0% schema coverage. Minor cost only from an inline list that could be formatted more scannably.

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

Completeness5/5

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

For a one-parameter read-only list tool with no output schema, it covers what is enumerated (per-kind), what a bookmark retains (params, not results), and what to do next. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema coverage is 0% and `kind` has no description or enum, so the description carries the full burden and delivers: it enumerates all ten accepted values (news, gservice-trends, gservice-maps, twitter-trends, tt-trends, yt-trends, ig-trends, rd-trends-search, rd-trends-subreddit, tg-finder) and notes the tg-finder case uses `query`. This is exactly the meaning the schema omits.

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 verb and resource ('The caller's saved trend searches (bookmarks) of one list') and scopes it to a single kind, which cleanly separates it from create_trends_bookmark and delete_trends_bookmark. An agent can identify the operation without opening the 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?

Explicitly tells the agent what to do with the result: 'run it again with the matching list/search tool', which frames the listing as a discovery step. It does not explicitly name the read-vs-create/delete alternative tools, but the resource name and scoping make the intended use clear.

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.