Skip to main content
Glama

Update a saved search

update_saved_search
DestructiveIdempotent

Use this when the user wants to rename a saved search or replace its filters. New filters replace the old ones entirely. Its kind (people or companies) cannot change. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "savedSearchId": "<savedSearchId>"
    },
    "name": "update_saved_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoA new title.
filtersNoNew filters, replacing the old ones, in the saved search's own kind.
savedSearchIdYesThe saved search's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The description adds real value beyond that: it warns that new filters replace old ones entirely (what gets destroyed), states that the kind is immutable, and notes the call is 'Free', which is cost information an agent cannot get from structured fields.

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?

Four short sentences, front-loaded with the trigger condition, then the two behavioral constraints, then a one-word cost note. Nothing is padded and every sentence carries information an agent would otherwise have to infer.

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 3-parameter mutation with rich annotations and no output schema, the description covers the main hazards: replacement semantics, immutability of kind, and cost. It does not say whether omitting title leaves it unchanged, which is the one remaining partial-update ambiguity.

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 title, filters, and savedSearchId, including that filters are 'in the saved search's own kind'. The description's replacement semantics and immutability of kind largely restate the schema, so it stays at the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states specific operations on a specific resource: rename a saved search or replace its filters. It also states an invariant (kind cannot change), which lets an agent distinguish this from generic update tools. It does not name any sibling, but the resource itself is unambiguous.

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 opening 'Use this when the user wants to rename a saved search or replace its filters' is explicit trigger guidance tied to user intent. It gives no when-not conditions or named alternatives, but the intent framing is strong enough to select the tool with confidence.

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