Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

delete_media_legacy

Deletes media by mediaId through the deprecated POST alias kept for backward compatibility; use DELETE /media/{mediaId} for new integrations.

Instructions

Deprecated. Use DELETE /media/{mediaId} instead.

This POST alias is kept for backward compatibility with earlier integrations. New integrations should call DELETE /media/{mediaId}: 1msg follows REST conventions for resource deletion going forward (delete a resource with the DELETE verb on its resource path).

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": {
      "mediaId": "<mediaId>"
    },
    "name": "delete_media_legacy"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose that this is a destructive deletion and that it is deprecated, but it says nothing about irreversibility, required permissions, behavior when mediaId does not exist, or the response — all material for an unannotated mutation tool.

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?

Front-loaded with the deprecation notice, which is the single most important fact. The closing explanation of 1msg's REST conventions is mildly redundant padding but not harmful.

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 one-parameter deprecated alias with no output schema, the migration signal is the essential content and it is present. However, key facts for calling it safely — destructive/irreversible nature, error semantics, and parameter meaning — are absent, and no annotations exist to fill the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the single `mediaId` parameter. It only echoes the name inside a URL template; it does not say whether mediaId is the media's own ID, a message ID, what format it takes, or that it is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states in plain terms that this tool deletes a media object; the purpose is only inferable from the referenced endpoint path `DELETE /media/{mediaId}` and the `_legacy` name. It does name a replacement endpoint, but it points at the HTTP route rather than the sibling MCP tool `delete_media`, which is what an agent actually selects between.

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

Usage Guidelines4/5

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

Strong, explicit guidance: 'Deprecated. Use ... instead' plus 'kept for backward compatibility with earlier integrations' tells the agent exactly when not to use it. It stops short of a 5 because the alternative is expressed as an HTTP path rather than the sibling tool name `delete_media`, forcing the agent to map one to the other.

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