Skip to main content
Glama

PickedJobs

List saved searches

list_saved_searches
Read-onlyIdempotent

This account’s saved job searches: id, name, filters, and email alert setting and frequency. Does not use the job allowance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_saved_searches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely non-obvious facts: that the call does not consume the job allowance, and what fields are returned (valuable since no output schema exists). It stops short of noting pagination, ordering, or result limits.

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?

Two short sentences with zero filler, and the returned-field list is front-loaded ahead of the quota note. The phrasing 'email alert setting and frequency' is slightly compressed but still 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 zero-parameter read with no output schema, the definition covers what comes back and its cost, which is what an agent needs. Remaining gaps (ordering, pagination, whether all saved searches are returned) are minor for a per-account list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so parameter semantics default to the baseline. Nothing in the description misleads about inputs, and the mention of filters/email alert settings clearly refers to returned data rather than accepted arguments.

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 names the specific resource (this account's saved job searches) and enumerates the returned fields (id, name, filters, email alert setting and frequency). The verb 'list' is carried only by the name/title, but the resource and scope are unambiguous enough to distinguish it from save_search 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 Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternatives despite siblings like save_search and delete_saved_search that an agent might confuse it with. The only contextual hint is the quota note, which tells the agent it is cheap to call but not when to call it.

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