Use saved searches

Use saved-search MCP tools when an agent needs to preserve a useful GovTribe search, find a previously saved search, reopen its current results, or update its notification cadence. Saved searches store a search definition so the user or workspace can return to the same search later.

What saved searches store

A saved search can include the source search type, query, filters, sorts, search mode, frequency, owner or creator context, view-results URL, and a search_persistence_id. The exact fields available to the agent come from Search saved searches MCP tool.

Use Source identifiers and record matching when you need to distinguish a saved-search govtribe_id, a search_persistence_id, and a view_results_url.

Create a saved search

Create a saved search only after a Search_* tool returns a search_persistence_id for the useful search state. Name the saved search for the user-facing market, buyer, topic, or workflow it will support.

Tool: Create_Saved_Search

{
  "search_persistence_id": "<SEARCH_PERSISTENCE_ID>",
  "name": "Counter UAS opportunities due in the next 12 months",
  "frequency": "Daily"
}

Choose Never when the user wants to preserve the search without email notifications. Choose Instant, Daily, or Weekly only when the user has asked for monitoring or notifications.

Find existing saved searches

Use Search_Saved_Searches when the agent needs to find a saved search by name, owner, creator, scope, or saved-search ID.

Tool: Search_Saved_Searches

{
  "query": "\"Counter UAS\"",
  "fields_to_return": [
    "govtribe_id",
    "name",
    "frequency",
    "q",
    "filters",
    "sorts",
    "view_results_url",
    "search_persistence_id"
  ],
  "per_page": 10
}

Review the returned q, filters, sorts, and searches_govtribe_type before deciding whether a saved search is the one the user meant.

Reopen current results

Use the saved search's view_results_url when the user wants the GovTribe Web page. Use the saved search's stored q, filters, sorts, and searches_govtribe_type when the agent needs to continue analysis through MCP tools.

If the task needs row-level records, rerun the matching Search_* tool with the saved search's query and filters. Request only the fields needed for the current step.

Update a saved search

Use Update_Saved_Search when the user asks to rename a saved search or change notification frequency.

Tool: Update_Saved_Search

{
  "saved_search_id": "<SAVED_SEARCH_ID>",
  "name": "Counter UAS opportunities - active review",
  "frequency": "Weekly"
}

Do not update a saved search just because a new search returned better results. Create or update only when the user asks to preserve, rename, or change notifications for a saved search.

Saved search versus shared search

A saved search is a workspace record with a name and optional email cadence. A shared search or view_results_url opens a search state in GovTribe Web but does not by itself create a saved-search record.

Use a saved search when the user wants to revisit, monitor, or manage the search later. Use a URL when the user only needs to open or share the current result set.

Related articles

• Search saved searches MCP tool: Find saved-search records and inspect saved query definitions.
• Create saved search MCP tool: Create a saved search from a search persistence ID.
• Update saved search MCP tool: Rename a saved search or change notification frequency.
• Choose a search mode and write queries: Shape a search before preserving it.
• Troubleshoot search results: Adjust a search before saving it when results are too broad or too narrow.