Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Delete a saved query

saved_queries_delete
Destructive

Permanently delete a saved query along with its versions, runs, and stored matches to remove obsolete query data. This action cannot be undone.

Instructions

Delete a saved query with its versions, runs and stored matches. This can't be undone.

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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "saved_queries_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe saved query's id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is established structurally. The description earns credit for disclosing the cascade scope (versions, runs, stored matches are removed) beyond what annotations say, but adds nothing about permissions, error behavior on a missing id, or rate limits.

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?

Two short sentences with zero waste: the cascade scope comes first and the irreversibility warning second. Every clause earns its place.

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 simple destructive single-id operation with full schema coverage and a clear annotation safety profile, this is nearly complete. It stops short of 5 because it says nothing about what happens when the id does not exist (error vs silent success), which matters for a non-idempotent delete.

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 all four parameters — including the meta parameters context, llm_model, and conversation_id — are documented in the schema itself. The description adds no meaning beyond the schema, making the baseline 3 correct.

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?

Names a specific verb and resource ("Delete a saved query") and adds scope via the cascade list (versions, runs, stored matches). It does not explicitly distinguish itself from saved_queries_update or saved_queries_get, but the delete verb plus the sibling naming convention makes disambiguation clear without opening the schema.

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 or when-not-to-use guidance. It never points to saved_queries_update as the non-destructive alternative when a user only wants to change a query, so an agent gets only the implied "use this to delete" signal.

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