Skip to main content
Glama

preview_delete_list

Avoid accidental data loss by previewing a SharePoint list deletion. Provide a listId to review the deletion impact.

Instructions

Preview deleting a list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYes
Behavior1/5

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

With no annotations provided, the description carries the full burden of explaining behavior. It fails to state whether the tool modifies the list, returns a dry-run result, or is safe. The word 'preview' implies non-destructive but does not explicitly disclose this critical behavioral trait.

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

Conciseness2/5

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

The description is extremely brief (one sentence), but brevity here is under-specification rather than appropriate conciseness. It omits essential information about the tool's purpose, behavior, and parameters.

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

Completeness1/5

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

Given the lack of annotations and output schema, the description is woefully incomplete. It does not explain what a 'preview' returns, whether state changes, or how to interpret results, making it impossible for an agent to use the tool correctly without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one required parameter 'listId' with no description, and schema description coverage is 0%. The description 'Preview deleting a list' does not explain what 'listId' refers to or how to obtain it, leaving the agent without any additional meaning beyond the parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Preview deleting a list.' simply restates the tool name 'preview_delete_list' without adding clarity about what 'preview' means or what the tool actually does. It does not explain the difference from 'delete_list' or what a preview entails.

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 guidance is provided about when to use this tool versus alternatives like 'delete_list' or 'preview_list_update'. There is no mention of calling this before deletion or any conditions under which this tool is appropriate.

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/icemage001/local_sharepoint_mcp'

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