Moxlade — Upwork buyer intelligence

Delete a saved search

delete_saved_search

DestructiveIdempotent

Delete a saved search and its delivery, permanently.

saved is the slug list_saved_searches returns — not the display name.

THIS CANNOT BE UNDONE and there is no archive: the search and its webhook are removed, and re-creating it means calling save_search again with the filter, which you would need to have kept. Postings already delivered are yours and are unaffected; nothing further will be.

Do NOT use it to pause. There is no pause tool because there is nothing to call: letting a plan lapse pauses every saved search on the token, and paying resumes them where they left off. Deleting to stop delivery for a month throws the filter away to solve a problem that solves itself.

Returns deleted (false, with a note, when no search on this token has that slug — a delete that matched nothing is an answer, not an error) and the saved slug it acted on.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`saved`	Yes	The slug list_saved_searches returns — not the display name. Deleting one that is already gone answers false rather than failing.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	Why nothing was deleted, when nothing was.
`saved`	No	The slug acted on.
`deleted`	No	False, with a note, when no search on this account had that slug — an answer, not an error.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructive and idempotent hints, the description details permanent removal, no archive, webhook deletion, impact on already-delivered postings, and the non-error behavior when deleting a nonexistent slug. This is rich behavioral context that annotations alone do not convey.

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?

Although lengthy, the description is well-structured and every paragraph earns its place for a destructive operation. The key action is front-loaded, followed by parameter clarification, irreversible consequences, usage warnings, and return semantics.

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

Completeness5/5

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

The description covers what happens, what cannot be undone, how to avoid misuse, what is returned, and how the action relates to sibling tools. With an output schema and detailed annotations present, nothing essential is missing for an agent to call this correctly.

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 schema already fully documents the single parameter, including the slug-vs-display-name distinction. The description repeats this same point and adds surrounding context, but it does not add new parameter-level meaning beyond what the schema provides.

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 states a specific action and resource: 'Delete a saved search and its delivery, permanently.' This clearly distinguishes it from save_search and list_saved_searches, and the title reinforces the same meaning without adding ambiguity.

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

Usage Guidelines5/5

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

The description explicitly warns 'Do NOT use it to pause' and explains the correct alternative: letting a plan lapse pauses saved searches. It also notes that re-creating a deleted search requires calling save_search again with the filter, giving an agent clear decision rules.

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

All Moxlade — Upwork buyer intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool maps to a distinct resource or action: search, filter validation, saved-search management, buyer lookup, buyer quality, job scoring, market rates, and account/plan introspection. The get_* tools are cleanly separated by complements such as get_job vs get_job_score and get_buyer vs get_buyer_quality, so an agent should not struggle to pick the right one.

Naming Consistency5/5

All tool names consistently use snake_case verb_noun or verb_adjective_noun patterns, such as search_jobs, check_prefilter, delete_saved_search, and get_buyer_quality. There are no camelCase names, vague verb-only names, or mixed conventions.

Tool Count5/5

At 15 tools, the server sits exactly within the ideal range and each tool earns its place in the workflow. The set covers discovery, enrichment, saved-search lifecycle, and account introspection without obvious redundancy.

Completeness4/5

The core workflow is well covered: search, prefilter validation, job detail, scoring, buyer identity, payment quality, saved-search create/list/delete, and plan/activity visibility. The main gap is the lack of an update operation for an existing saved search, such as changing its filter or attaching a webhook later; this is a minor workaround rather than a blocking dead end.

Resources

Need Help?