Skip to main content
Glama

Get a saved search

get_saved_search
Read-only

Use this when you need one saved search's title, kind and stored filters, for example before changing it. 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": "get_saved_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
savedSearchIdYesThe saved search's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds cost context with 'Free.' and implies a safe single-record read, but says nothing about what happens when the id is unknown or about permissions.

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?

One front-loaded sentence plus a one-word cost note; nothing is redundant. The compressed phrasing ('title, kind and stored filters, for example before changing it') is terse but readable.

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 one-parameter read tool with full annotations, the description is close to sufficient, and it usefully enumerates the returned fields in place of a missing output schema. Only edge-case behavior (not-found, permission errors) is unaddressed.

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%, so the single savedSearchId parameter is already documented in the schema, and the description adds nothing about its 24-character hex format or source. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb+resource ('get one saved search') and names the returned fields (title, kind, stored filters), which distinguishes it from list_saved_searches and run_saved_search by implication of 'one'. It stops short of explicitly naming those siblings, so differentiation relies on the word 'one'.

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?

Gives a concrete usage trigger ('use this when you need one saved search's...') and a scenario ('before changing it') that points at the read-before-update pattern around update_saved_search. No explicit exclusions or named alternatives, which keeps it below a 5.

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