Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

delete_media

Delete one or more media library items by their IDs to remove outdated or unwanted assets from the library.

Instructions

Delete one or more items from the media library by their IDs.

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": {
      "ids": "<ids>"
    },
    "name": "delete_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesOne or more media IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a destructive operation, yet it says nothing about permanence, partial-failure behavior for multiple IDs, permission requirements, or consequences for posts referencing the media. It communicates only the bare mutation, leaving the risk profile undisclosed.

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?

One sentence, front-loaded with the verb and free of padding. It is efficient, though its brevity leaves no room for the warnings a delete tool arguably needs.

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 an irreversible mutation with no annotations and no output schema, an agent needs to know the scope of deletion, failure semantics for multiple IDs, and any side effects. The description supplies none of these, so it is insufficient for the tool's risk level.

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% and the single 'ids' array is documented with a description and minItems constraint. The description adds nothing beyond the schema, so the baseline 3 applies.

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 and resource ('Delete ... items from the media library') and identifies the selection key ('by their IDs'). It is unambiguous against siblings like list_media or update_post, though it does not explicitly name an alternative or boundary.

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 guidance on when to use this tool versus alternatives, nor any stated prerequisites such as ownership or whether the media must be unattached from posts. The agent must infer all usage context from the name alone.

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