Skip to main content
Glama
Sign In
carsearch-mcp

carsearch-mcp

by Lironktf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

run_saved_search

Executes a saved search to incrementally crawl for new car listings, including deal/project scores and triggered alerts.

Instructions

Run a saved search now: crawls incrementally, returns new listings (with deal/project scores) and any alerts triggered.

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": {
      "name_or_id": "<name_or_id>"
    },
    "name": "run_saved_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_pagesNo
name_or_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It meaningfully discloses that the tool 'crawls incrementally' rather than just fetching, and that it returns alerts. It does not mention side effects, latency, or authentication needs, but the key execution semantics are conveyed.

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 a single well-structured sentence with no filler. The core action is front-loaded ('Run a saved search now') and the key outputs are listed immediately after the colon.

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

Completeness3/5

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

Given the output schema exists, the description adequately conveys the main behavior and return highlights. However, it is incomplete around parameter usage, especially max_pages, and provides no safety or side-effect guidance in the absence of annotations.

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

Parameters2/5

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

The schema has 0% description coverage and the description adds no parameter-specific meaning. name_or_id is fairly inferable from its title, but max_pages is unexplained, and the description does not compensate for the schema's lack of guidance.

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 clearly identifies the action ('run'), the resource ('saved search'), and the expected outputs (new listings with deal/project scores and triggered alerts). This distinguishes it from sibling tools that create, list, or delete saved searches.

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

Usage Guidelines3/5

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

The intended use case is implied: execute an existing saved search to get new listings and alerts. However, there is no explicit guidance about when to prefer this over related siblings like search_cars, get_new_listings, or list_saved_searches.

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

Deploy Server

Other Tools