ESQ Matching Engine

Save or change search filters

update_listing_criteria

DestructiveIdempotent

Save or change search filters (location, budget, timing, practice area, language, sort priorities) for this conversation. No personal contact details. Deleted automatically after 24 hours. This is a listing service, not a lawyer referral service. No lawyer pays for placement or ranking of any kind.

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": {
      "criteria": "<criteria>"
    },
    "name": "update_listing_criteria"
  }
}

Input Schema

Name	Required	Description
`criteria`	Yes	Fields to set or change. Do not include names, emails or phone numbers.
`clear_fields`	No
`preference_set_id`	No	Omit to create a new set

Output Schema

Name	Required	Description	Default
`note`	Yes
`criteria`	Yes
`retention`	Yes
`expires_at`	Yes
`preference_set_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / criteria / properties / description / description

Previous value: -"Short description of the legal need in the user's words. Used only to pick a practice area; not stored."New value: +"Short description of the legal need in the user's words. Used only to pick a practice area and to notice a cost concern (then free and low-cost options are shown); not stored."

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / criteria / properties / priorities / description

Previous value: -"What matters most, in order. Shifts ranking weights."New value: +"Older way to pick an order; used only when sort is not given (price: published_fees_first, speed: availability_reported_first, experience: years_licensed, proximity: nearest_office)."

AddedNov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description adds meaningful context beyond annotations: automatic deletion after 24 hours, a prohibition on personal contact details, and a clear statement that this is a listing service with no paid placement. It does not explain merge-vs-replace semantics for updating criteria, what destructive behavior is implied by destructiveHint=true, or how clear_fields interacts with saving.

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?

The description is four short sentences, front-loaded with the core action, and every sentence carries relevant information about scope, privacy, retention, or service model. It is efficient, though the trust-related disclaimers could be slightly compressed.

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?

For a complex tool with a large nested criteria object and output schema, the description covers purpose, privacy constraints, and service-model context well. It is incomplete on update semantics — whether fields merge or replace, how clear_fields works, and how to read existing criteria — which matter for correct invocation.

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?

The description summarizes the kinds of criteria that can be set (location, budget, timing, practice area, language, sort priorities), which helps orient the agent. But it does not mention clear_fields or preference_set_id semantics, and with only 67% schema coverage those undocumented parameters rely on the schema alone.

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 a specific verb (save/change), resource (search filters), and scope (this conversation), and enumerates the filter categories covered. It does not explicitly distinguish itself from siblings like get_search_filters or update_matching_preferences, so an agent must infer the boundary.

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?

Usage is implied by 'Save or change search filters ... for this conversation,' which tells the agent to call it when criteria need to be set or modified. However, there is no explicit when-not guidance, no mention of reading filters via get_search_filters, and no explanation of how it differs from update_matching_preferences.

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

All ESQ Matching Engine tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?