Skip to main content
Glama

Klinio

List searches

list_searches
Read-only

The account's history, newest first: every search started on klinio.io, in the Chrome extension, with the API or here. Filters: q (text in its name), status, source, since, until.

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

Input Schema

NameRequiredDescriptionDefault
qNoText in the search's name or words.
limitNoSearches per page (default 20).
sinceNoA date (2026-11-01) or ISO 8601 time: searches started from then.
untilNoA date or ISO 8601 time: searches started up to then (a date includes the whole day).
cursorNoThe next_cursor of the previous page.
sourceNogoogle_maps, google_search, clutch, linkedin, linkedin_list, websites or merged (several separated by commas).
statusNoqueued, running, completed, stopped or failed (several separated by commas).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds genuinely new behavior: result ordering (newest first) and the fact that all channels are included. It says nothing about pagination/next_cursor flow or result volume, which are the behaviors an agent most needs for a list endpoint, so the added context is real but partial.

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?

Two dense sentences with the scope and ordering front-loaded before the filter list; nothing is padded. The colon-and-list structure in the second sentence is efficient, though the first sentence's clause stack ('on klinio.io, in the Chrome extension, with the API or here') is slightly awkward to parse.

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?

For a read-only, seven-optional-parameter listing tool with full schema coverage and no output schema, the description covers purpose, ordering, and filter surface, but leaves out pagination mechanics (cursor/next_cursor flow) and default page size, both of which shape how an agent drives this tool. Adequate rather than complete.

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 schema already documents all seven parameters, including limit defaults and comma-separated multi-values for status/source. The description restates five of them and actually narrows q to 'text in its name' while the schema says 'name or words', adding no meaning beyond the schema and slightly understating it.

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 names the resource (the account's search history) and its ordering (newest first), and enumerates the channels covered (klinio.io, Chrome extension, API, 'here'), which lets an agent tell this apart from get_search (single search) and get_results (outputs). The verb is implicit in 'history' rather than stated as 'list', so it is clear but not maximally sharp.

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?

The enumeration of filters (q, status, source, since, until) implies when the tool is useful — browsing or filtering searches — but there is no explicit when-to-use/when-not guidance and no sibling named as an alternative (e.g., get_search for a known search ID, get_results for a search's output). The cross-channel scope statement helps the agent decide coverage, but routing is left to inference.

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