Skip to main content
Glama

save_search

UNDERSTANDING — Persist the current search criteria as a named saved search you own, so you can re-run it and get net-new results later. Criteria use the same filters as apis_io_search. Requires an apis.io API key. Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
qNoFree text over name + description, e.g. "sms".
areaNoArea slugs, e.g. ["security"].
bandNoexemplar | strong | developing | thin | minimal.
nameYesName for the saved search, e.g. "EU payments, strong+".
tagsNoTag slugs, e.g. ["payments"]. On providers: what the company does (see api_tags).
matchNoHow `tags` combine: any (default) or all.any
regionNoRegion slugs, e.g. ["north-america"].
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
industryNoIndustry slugs, e.g. ["fintech"].
min_scoreNoMinimum Kin Score composite (0-100), e.g. 60.
artifact_typesNoArtifact types required, e.g. ["OpenAPI"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Area slugs, as find_areas returns them, e.g. [\"security\"]."New value: +"Area slugs, e.g. [\"security\"]."
    • changedInput schema / properties / artifact_types / description
      Previous value: -"Artifact types an API must carry, e.g. [\"OpenAPI\",\"AsyncAPI\",\"Postman\"]. Synonyms fold (MCPServer = MCP)."New value: +"Artifact types required, e.g. [\"OpenAPI\"]."
    • changedInput schema / properties / band / description
      Previous value: -"Rating bands: exemplar, strong, developing, thin, minimal."New value: +"exemplar | strong | developing | thin | minimal."
    • changedInput schema / properties / context / description
      Previous value: -"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."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / industry / description
      Previous value: -"Industry slugs, as find_industries returns them, e.g. [\"artificial-intelligence\"]."New value: +"Industry slugs, e.g. [\"fintech\"]."
    • changedInput schema / properties / match / description
      Previous value: -"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."New value: +"How `tags` combine: any (default) or all."
    • changedInput schema / properties / min_score / description
      Previous value: -"Only providers whose Kin Score composite is at or above this, 0-100, e.g. 60."New value: +"Minimum Kin Score composite (0-100), e.g. 60."
    • changedInput schema / properties / q / description
      Previous value: -"Free text over name + description."New value: +"Free text over name + description, e.g. \"sms\"."
    • changedInput schema / properties / region / description
      Previous value: -"Region slugs, as find_regions returns them, e.g. [\"north-america\"]."New value: +"Region slugs, e.g. [\"north-america\"]."
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."New value: +"Tag slugs, e.g. [\"payments\"]. On providers: what the company does (see api_tags)."
  2. Changed7 schema fields changed
    • addedInput schema / properties / area / description
      Added value: +"Area slugs, as find_areas returns them, e.g. [\"security\"]."
    • addedInput schema / properties / artifact_types / description
      Added value: +"Artifact types an API must carry, e.g. [\"OpenAPI\",\"AsyncAPI\",\"Postman\"]. Synonyms fold (MCPServer = MCP)."
    • addedInput schema / properties / industry / description
      Added value: +"Industry slugs, as find_industries returns them, e.g. [\"artificial-intelligence\"]."
    • addedInput schema / properties / match / description
      Added value: +"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."
    • addedInput schema / properties / min_score / description
      Added value: +"Only providers whose Kin Score composite is at or above this, 0-100, e.g. 60."
    • addedInput schema / properties / name / description
      Added value: +"Name for the saved search, e.g. \"EU payments, strong+\"."
    • addedInput schema / properties / region / description
      Added value: +"Region slugs, as find_regions returns them, e.g. [\"north-america\"]."
  3. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."
  4. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."
  5. 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"
      +}
  6. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the agent knows it is a non-destructive write. The description adds real context beyond that: an API key is required, explicit pricing ($0.01/call, B1 tier, included in Understanding/Influence), a pointer to apis://prices, and the ownership semantics ('you own'). It does not, however, disclose what happens on a name collision.

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-loads the purpose in the first clause, then scoping, then cost/auth. Efficient and skimmable. The pricing sentence is the longest and is arguably table stakes rather than description content, but it is material to 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 an 11-parameter mutation with no output schema, the description covers the essentials an agent needs: what it creates, ownership, required auth, cost, and the filter vocabulary source. Missing duplicate-name/overwrite behavior, which matters for a persistent-write tool, keeps it short of a 5.

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% with 11 well-documented parameters, so the schema carries the semantic load and baseline is 3. The description's only parameter-relevant contribution is that the criteria reuse apis_io_search's filter vocabulary, which is orientation, not new per-parameter meaning.

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+resource ('Persist the current search criteria as a named saved search you own') and adds the downstream benefit (re-run for net-new results). An agent can distinguish it from run_saved_search, list_saved_searches, and delete_saved_search without opening any schema.

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?

Implies when to use it by stating the payoff ('so you can re-run it and get net-new results later') and cross-references apis_io_search for the filter set, but never states when-not to use it or routes the agent to run_saved_search / saved_search_net_new. Usage is inferable rather than explicit.

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