skylight-mcp

skylight_remove_from_album

Remove messages or photos from one or more albums by specifying album IDs and message IDs.

Instructions

Remove messages/photos from albums.

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": {
      "album_ids": "<album_ids>",
      "message_ids": "<message_ids>"
    },
    "name": "skylight_remove_from_album"
  }
}

Input Schema

Name	Required	Description	Default
`frameId`	No
`album_ids`	Yes
`message_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.1Sep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed4 schema fields changedv0.7.1Aug 29, 2026
- removedInput schema / properties / album_ids / items / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / album_ids / items / type
```
Added value: +[
+  "string",
+  "number"
+]
```
- removedInput schema / properties / message_ids / items / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / message_ids / items / type
```
Added value: +[
+  "string",
+  "number"
+]
```
First observedv0.4.6Jul 30, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safe direction is partly covered, but the description adds nothing beyond them. The critical question — whether removal merely detaches a message from an album or destroys the underlying message — is left unresolved despite sibling delete tools existing.

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?

A single short sentence with the action front-loaded and no filler. It is efficient, though its brevity is achieved by omitting rather than by compressing essential detail.

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 a mutation tool with 0% parameter description coverage, no output schema, and no guidance on return or side effects, one sentence is not enough. The agent cannot tell the remove/delete boundary or what frameId does before calling it.

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 carry three parameters but only loosely gestures at two ('messages/photos' and 'albums'). The optional frameId is never mentioned, and nothing explains how album_ids and message_ids relate (i.e. whether each message is pulled from all listed albums).

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?

States a specific verb (Remove) and resource (messages/photos from albums), which is clearer than a tautology. However it does not differentiate itself from siblings that also detach or delete content, such as skylight_add_to_album's inverse relationship or skylight_delete_messages/delete_message, leaving the agent to infer whether this unlinks or destroys.

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?

No when-to-use guidance and no mention of alternatives. The obvious counterpart, skylight_add_to_album, is never referenced, nor is the boundary with delete_messages/delete_message, which matters because 'remove' and 'delete' are easily conflated here.

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

Deploy Server