Skip to main content
Glama

LeadMarina

List advanced searches

list_advanced_searches
Read-onlyIdempotent

This account's advanced searches, newest first: status, leads so far, searches done of total. The newest limit, plus any still running or paused past them.

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_advanced_searches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoUp to 100; 25 by default.

Output Schema

NameRequiredDescriptionDefault
advanced_searchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are newest-first, and the limit is not a hard cap because running or paused searches are appended past it — a non-obvious inclusion rule an agent would otherwise miss.

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 short sentences, front-loaded with resource and ordering, with zero filler. The field list is a telegraphic fragment ('status, leads so far, searches done of total') that reads slightly run-on but is still parseable and earns its space.

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 zero-required-param, read-only list tool with an output schema, the description covers ordering, inclusion semantics, and row contents. It does not address whether results are paginated or how they relate to list_searches, but nothing critical for calling it correctly is missing.

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 100% ('Up to 100; 25 by default'), so the schema already carries the range and default. The description goes beyond it by explaining that the limit selects the newest N and that in-flight searches are returned in addition, clarifying what the parameter actually bounds.

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 (this account's advanced searches), the ordering (newest first), and the per-row fields (status, leads so far, searches done of total), which is enough to distinguish it from get_advanced_search and estimate_advanced_search. It never explicitly says 'list' or names a sibling, but the resource and shape are unambiguous.

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 when-to-use or when-not-to-use guidance is given. With siblings like list_searches, get_advanced_search, and list_automations present, the agent gets no signal about which listing tool to pick for which need; the only implied usage comes from the resource noun itself.

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.