Skip to main content
Glama

skylight_delete_list_item

Destructive

Remove a specific item from a Skylight frame's list by providing its list ID and item ID. Keeps your displayed lists accurate and up to date.

Instructions

Delete a list item from a Skylight frame.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes
listIdYes
frameIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv0.4.6

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds a small amount of context by specifying that the item is deleted from a Skylight frame, but it does not disclose irreversibility, side effects, or what happens to related data.

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?

The description is a single, front-loaded sentence with no wasted words. It directly states the action and resource without filler or repetition.

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 destructive tool with three parameters, no output schema, and no parameter-level descriptions, this description is too thin. It lacks guidance on required identifiers, optional frameId behavior, and the consequences of deletion, and it does not help an agent choose between this and the sibling bulk-delete tools.

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 compensate, but it does not explain listId, itemId, or the optional frameId. The phrase 'a list item' and 'Skylight frame' give only weak hints about the parameter meanings; property names themselves carry most of the semantics.

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?

The description states a clear verb and resource: delete a single list item from a Skylight frame. It is distinct from bulk deletion or list deletion in the sibling set, though it does not explicitly differentiate itself from skylight_delete_list_items or skylight_clear_list.

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?

The description provides no guidance on when to use this tool versus alternatives such as skylight_delete_list_items for bulk deletion or skylight_clear_list for clearing a whole list. Usage is only implied by the name and the single-sentence description.

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