Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Delete a monitor

monitors_delete
Destructive

Permanently delete a monitor by ID. Use this to remove a monitor you no longer need, since deletion cannot be undone.

Instructions

Permanently delete a monitor. Cannot 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": "monitors_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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

C2.9/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, so "permanently... cannot be undone" largely restates the structured signal rather than adding to it. The description says nothing about whether associated checks, events, or sources are also removed, whether any auth or ownership scoping applies, or what the call returns.

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 the permanence warning front-loaded and no filler. It is efficient, though the brevity comes at the cost of content rather than being tight-but-complete.

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

Completeness2/5

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

For a destructive mutation with no output schema, the definition is thin: it does not say what collateral data is destroyed, whether deletion is scoped to a workspace, or how failures surface. The annotations cover the safety flag and the schema covers the parameters, but the blast radius of this call remains undisclosed.

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 coverage is 75% and the one undocumented parameter (id) is self-evident, so the schema carries most of the burden. The description adds no meaning about the id, nor about the required context/llm_model/conversation_id envelope parameters, leaving that entirely to the schema.

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?

States a specific verb and resource ("Permanently delete a monitor") that unambiguously separates it from monitors_update, monitors_get, and monitors_list. It does not explicitly name a sibling, but no agent would confuse it with a read or update operation.

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?

No when-to-use guidance and no alternatives are named. It never suggests that monitors_update might be the safer path for pausing/disabling instead of deleting, nor does it state any precondition such as confirming the monitor exists or is not in active use.

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