Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_delete_messages

Destructive

Permanently delete messages or photos from a Skylight frame in bulk; a confirmation preview is required first since deletions cannot be undone.

Instructions

Bulk-delete messages/photos from the frame — permanent; there is no trash, and a photo on the frame may exist nowhere else. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview lists every id with its caption, and the token binds that exact set. For one message use skylight_delete_message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameIdNo
message_idsYesMessage/photo ids to delete.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. 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"
+]
  4. First observedv0.4.6

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds critical behavioral context beyond them: deletion is permanent with no trash, a photo may exist nowhere else, and the tool enforces user confirmation via a preview/confirmToken flow. This is exactly the extra safety information an agent needs before calling a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the irreversible nature ('permanent; there is no trash') before explaining the confirmation protocol. Every sentence carries operational weight for a destructive tool, and the alternative-tool routing is placed at the end where it naturally follows the bulk-vs-single distinction.

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

Completeness5/5

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

Given the destructive nature, no output schema, and moderately covered parameters, the description covers the critical missing pieces: irreversibility, mandatory user confirmation, fallback mechanics, preview contents, and token binding. An agent has enough context to invoke this safely without additional documentation.

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 coverage is 67%. The description adds meaning beyond the schema by clarifying that the preview lists every id with its caption and that the confirmToken binds that exact set, plus reiterating that a repeat call must use the same arguments. It does not explain the frameId parameter, leaving one gap.

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 and resource: 'Bulk-delete messages/photos from the frame'. It also explicitly distinguishes itself from the single-item sibling by saying 'For one message use skylight_delete_message', so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Explicitly names the alternative tool and the condition that selects it ('For one message use skylight_delete_message'). It also describes exactly when the two-step confirmation fallback applies versus elicitation, giving complete usage context.

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