Skip to main content
Glama

FundingLandscape

by io.github.tettertotter

Update Saved Search

update_saved_search
Idempotent

Update a saved search. Modify query, filters, alert cadence, name, or quality settings. Can only update your own saved searches.

MODIFIABLE FIELDS: query, name, filters (same schema as save_search), cadence (weekly/daily/never), hidelow (quality filter), emailEnabled (on/off)

TIP: Call list_saved_searches first to see the current settings, then update only the fields that need to change. The response confirms what was updated.

Does not count toward your monthly searches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSaved search ID to update
nameNoNew friendly name
queryNoNew search query text
cadenceNoNew alert frequency. daily requires a paid plan (Plus or Pro); free includes weekly. never = turn email alerts off.
filtersNoNew filters (same schema as save_search filters). Replaces all existing filters.
hidelowNoHide low-confidence results in alerts.
emailEnabledNoEnable or disable email alerts without changing cadence.

TDQS

A4.2/5.0
Behavior4/5

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

Adds 'Can only update your own saved searches' (permission), 'Does not count toward your monthly searches' (quota), and 'The response confirms what was updated' (return behavior). These go beyond annotations. Doesn't mention that filters are replaced wholesale, but schema covers that.

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?

Three short paragraphs, each with a distinct purpose: intro, modifiable fields, tip/quota. No unnecessary words.

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?

Covers the key aspects: what it does, auth constraint, quota, and response behavior. With a high-coverage schema, this is sufficient, though it could clarify behavior when only id is supplied.

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 covers 100% of parameters, so description's MODIFIABLE FIELDS list largely restates schema. The cross-reference to save_search schema for filters is useful, and the cadence enum values are repeated, but no additional semantic depth is added.

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?

Description opens with 'Update a saved search' and lists modifiable fields (query, filters, cadence, name, quality settings). This clearly distinguishes it from siblings like save_search (create) and delete_saved_search.

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?

Tips to call list_saved_searches first and update only fields that need to change provide clear workflow. The restriction 'Can only update your own saved searches' sets a condition, but it doesn't explicitly say when to use this over save_search or delete_saved_search.

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

All FundingLandscape toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clear distinct purposes. Some overlap exists (e.g., search_grantsplus and search_foundations both return foundations, but descriptions clarify the distinction). Also batch_ variants are comprehensive versions of the standard searches. Overall, agents can differentiate well.

Naming Consistency4/5

Tool names predominantly follow verb_noun pattern in snake_case (e.g., search_grantsplus, get_opportunity, list_saved_searches). Minor deviation with 'whats_new' (no underscore) and 'check_connection' (different verb form). Otherwise consistent.

Tool Count4/5

26 tools is slightly above the typical 3-15 range but still reasonable for a comprehensive funding landscape server covering grants, procurement, foundations, saved searches, account management, and utilities. Each tool serves a clear purpose.

Completeness4/5

The tool surface covers core search, detail retrieval, saved search management, account information, and feedback. Missing are profile management or direct payment modification tools (only links provided). Minor gaps but overall complete for the domain.

Resources