Skip to main content
Glama

Delete Archived Shared Steps

delete_archived_shared_steps
DestructiveIdempotent

Permanently delete all archived shared steps from your project. Requires explicit confirmation to avoid unintended data loss.

Instructions

Permanently delete all archived shared steps in the current project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be set to True to proceed.
project_idNoOptional Allure TestOps project ID override.
output_formatNoOutput format: 'json' (default) or 'plain'.
Behavior3/5

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

Annotations already provide destructiveHint=true, indicating data destruction. Description adds 'permanently delete all' confirming irreversibility but does not disclose other traits like scope or authorization needs, which are not critical given annotation coverage.

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?

Single concise sentence with no filler. Front-loaded with the key action and resource. Every word contributes.

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

Completeness4/5

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

For a destructive tool with no output schema and simple parameters, the description covers the main purpose. Could mention irreversibility explicitly, but annotations compensate. Mostly complete.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. Description does not add parameter context beyond schema, which is acceptable since schema fully documents each parameter's purpose.

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?

Description clearly states the action (permanently delete) and resource (all archived shared steps) with specificity, distinguishing it from siblings like delete_shared_step which deletes any shared step.

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 explicit guidance on when to use this tool vs alternatives (e.g., delete_shared_step). The destructive hint is present but not elaborated in description. No when-not-to-use or prerequisites mentioned.

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/ivanostanin/lucius-mcp'

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