Skip to main content
Glama

apis-io

by io.apis
OverviewDiscussionsAdmin

list_saved_searches

Read-only

UNDERSTANDING — List the saved searches you own (name, criteria, when last run, how many matches are tracked). Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoOptional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes safety, and the description adds value with ownership scope, return fields, and pricing tier. It does not contradict the annotation. It is adequate for a read-only list operation, though it does not discuss pagination or possible absence of results.

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?

The description is compact and front-loads the core action and output fields. The pricing and plan inclusion sentences add useful context for cost-aware agents, though the 'UNDERSTANDING —' prefix and pricing link are not strictly necessary for invocation.

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 zero required parameters and no output schema, the description covers what the tool returns, ownership scope, and cost. Missing details like pagination or empty-result behavior are minor given the low complexity and the readOnlyHint annotation.

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% and the single optional 'context' parameter is fully explained in the schema, including when it is read and that it never affects ranking. With high schema coverage, the description need not repeat that detail, 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?

The description uses a clear verb and resource: 'List the saved searches you own, with the exact returned metadata ('name, criteria, when last run, how many matches are tracked'). It also distinguishes itself from siblings like save_search, run_saved_search, and delete_saved_search by clearly identifying itself as the listing operation.

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?

The description gives clear context: an agent should call this when the user wants to see their own saved searches and their tracked metadata. It does not explicitly name alternatives or exclude run_saved_search/delete_saved_search, but the listing intent is unambiguous from 'List the saved searches you own.'

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

All apis-io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources