Skip to main content
Glama

skylight_delete_messages

Delete multiple messages or photos from your Skylight frame at once by providing message IDs.

Instructions

Bulk-delete messages/photos from the frame.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameIdNo
message_idsYesMessage/photo ids to delete.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.7.1
    • removedInput schema / properties / message_ids / items / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / message_ids / items / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. First observedv0.4.6

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It communicates that the action is a deletion, but does not disclose whether deletion is permanent, whether it affects albums or shared copies, what happens to photos, or whether specific permissions are required.

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?

The description is a single front-loaded sentence with no filler words. It is efficient and easy to parse, though its brevity comes at the expense of behavioral guidance.

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?

This is a destructive bulk operation with no annotations, no output schema, and an undocumented optional frameId parameter. The description does not explain return behavior, scope constraints, or consequences of deletion, leaving an agent under-informed for a potentially irreversible action.

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?

The schema documents message_ids as 'Message/photo ids to delete', but frameId has no description. The tool description's reference to 'the frame' is not explicitly tied to frameId, and it does not clarify ID formats, whether frameId is optional, or how it scopes deletion.

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?

The description states a specific verb ('Bulk-delete'), a specific resource ('messages/photos'), and a location ('from the frame'). It distinguishes this tool from the sibling skylight_delete_message by emphasizing bulk deletion.

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

Usage Guidelines3/5

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

The word 'Bulk-delete' implies this is intended for deleting multiple messages/photos at once, and the singular sibling skylight_delete_message plausibly covers single deletions. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/skylight-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server