Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

delete_media

Delete previously uploaded media from the 1msg Chat API by numeric mediaId. Use this canonical endpoint to remove files returned by uploadMedia when they are no longer needed.

Instructions

Delete previously uploaded media by numeric mediaId (from /uploadMedia).

This is the canonical deletion endpoint and uses the REST DELETE verb on the media resource path. The older POST /deleteMedia is a deprecated alias.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.10
    • addedInput schema / properties / mediaId / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • removedInput schema / properties / mediaId / type
      Removed value: -"string"
  2. First observedv1.2.0

TDQS

A4/5.0
Behavior3/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. It adds useful behavioral framing by disclosing that this maps to a REST `DELETE` on the media resource path, which signals permanent removal, but it never explicitly says the operation is irreversible, what permissions/auth are required, or what happens if the media has already expired or been deleted.

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 core action and identifier, then a short paragraph on canonical-vs-deprecated routing. Every sentence is functional; the REST verb detail is slightly technical filler but supports the deprecation contrast rather than padding.

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 single-parameter deletion tool with no output schema, the definition covers what it does, where the ID comes from, and which alternative to avoid. It leaves out failure modes (already-expired media, unknown ID), permission requirements, and confirmation of destructive permanence, which matter for an irreversible operation.

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

Parameters4/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. It does: it identifies the parameter as a numeric `mediaId` and states its provenance (`from /uploadMedia`), which is exactly what an agent needs to source the value correctly. Minor tension remains since the schema permits string or number without explanation.

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?

States a specific verb (delete) and resource (previously uploaded media) keyed by a precise identifier (`mediaId`), and explicitly distinguishes itself from the `delete_media_legacy` sibling by naming the deprecated `POST /deleteMedia` alias. An agent can tell which deletion tool to pick without opening either schema.

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?

Clear routing context: this is the canonical deletion path and the older POST alias is deprecated, which effectively directs the agent to prefer this tool over `delete_media_legacy`. It stops short of stating when not to delete (e.g., media still referenced by an outbound message) or any preconditions such as ownership/permissions.

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