skylight_remove_from_album
Remove messages or photos from albums to keep your Skylight Calendar organized.
Instructions
Remove messages/photos from albums.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| frameId | No | ||
| album_ids | Yes | ||
| message_ids | Yes |
Remove messages or photos from albums to keep your Skylight Calendar organized.
Remove messages/photos from albums.
| Name | Required | Description | Default |
|---|---|---|---|
| frameId | No | ||
| album_ids | Yes | ||
| message_ids | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits such as whether removal is irreversible, if it requires specific permissions, or what happens to the messages after removal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, which is concise but lacks necessary detail. It could be expanded to include parameter information or usage context without becoming overly verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema, annotations, and parameter descriptions, the description is incomplete. It does not clarify the effect of the operation (e.g., whether messages are deleted or just unlinked) or prerequisites.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 3 parameters with 0% description coverage, and the description provides no explanation of their purpose or format. The description adds no value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (remove) and the objects (messages/photos from albums). However, it does not distinguish this from sibling tools like skylight_delete_message or skylight_delete_album, which could cause confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as deleting albums or messages entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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