Skip to main content
Glama

apis-io

by io.apis
OverviewDiscussionsAdmin

run_saved_search

Read-only

UNDERSTANDING — Re-run one of your saved searches against the live catalog and return current matching providers. 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
idYes
limitNo
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds pricing ($0.01 per call) and the 'live catalog' aspect, which are useful behavioral details beyond the annotation. It does not contradict the read-only hint and provides cost context that an agent would want to know.

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 sentences, front-loaded with the purpose, and a separate sentence for pricing. No fluff, and the pricing reference is useful. The 'UNDERSTANDING' prefix is a category label but doesn't waste 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 simple 3-parameter read-only tool, the description covers the core purpose and pricing. It doesn't explicitly mention how to obtain the saved search ID, but that is implied and can be inferred from sibling tools. The schema covers 'limit' and 'context' sufficiently, so the description is adequate for the complexity.

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

Parameters2/5

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

Schema description coverage is only 33% (only 'context' has a description). The tool description does not explain 'id' or 'limit' at all; it relies on the schema for types but the schema lacks descriptions for those fields. An agent would have to infer that 'id' is the saved search identifier, which is a gap given the low coverage.

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 states a specific action (re-run), the resource (saved searches), and the outcome (return current matching providers). It clearly distinguishes this from sibling tools like save_search, list_saved_searches, and delete_saved_search by focusing on re-execution against the live catalog.

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 implies you need an existing saved search ID to run this tool, which is clear from 're-run one of your saved searches'. It doesn't explicitly point to list_saved_searches for obtaining the ID or mention when not to use it, but the context is strong enough to guide an agent.

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