Skip to main content
Glama

Save Current Search

getmattered_create_saved_search

Save current job preferences as a named search and optionally enable email alerts for new matches. Use it to store searches for later review, not to change matching preferences.

Instructions

Save the user's current job preferences as a new named saved search, the same as saving a search on the dashboard. Pass name (optional; without one, the search is named after the first role and location) and alerts_enabled (optional; true emails the user new matches for this search). It adds a search and changes nothing else; it can be removed with getmattered_delete_saved_search. Nothing is sent to any employer and nothing is spent. Do not use it to change what the user is matched with; use getmattered_update_job_preferences. Next: getmattered_list_saved_searches.

Input Schema

NameRequiredDescriptionDefault
nameNoThe name of the new search, up to 120 characters. Without one, it is named after the first role and location.
alerts_enabledNotrue emails the user new matches for this search, false stops the emails.

Output Schema

NameRequiredDescriptionDefault
savedYesFrom getmattered_create_saved_search or getmattered_update_saved_search: the search after the change.
actionYesThe operation that ran: list, save, update or delete.
searchesYesFrom getmattered_list_saved_searches: every saved search.
deletedIdYesFrom getmattered_delete_saved_search: the search that was deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.2

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial context beyond annotations: it adds a search and changes nothing else, can be removed with the delete sibling, sends nothing to employers, and spends nothing. These details clarify the non-destructive, open-world=false behavior declared in annotations.

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?

The description is front-loaded with the action and optional parameters, then efficiently covers side effects, exclusions, and next steps. Every sentence contributes useful routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, annotations, and fully documented parameters, the description provides everything needed to select and invoke the tool correctly. It also routes to alternatives and follow-up tools.

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 coverage is 100%, so the schema already documents both name and alerts_enabled. The description restates their meaning, including the fallback naming behavior and email effect, but adds no meaningful semantics beyond what the schema provides.

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 verb and resource: saving the user's current job preferences as a new named saved search. It also distinguishes the tool from getmattered_update_job_preferences and identifies getmattered_delete_saved_search as the removal path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use getmattered_update_job_preferences to change what the user is matched with, and says not to use this tool for that purpose. It also identifies the next tool to call, getmattered_list_saved_searches.

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