Skip to main content
Glama

Unlink Shared Step

unlink_shared_step
DestructiveIdempotent

Remove a shared step reference from a test case so it no longer includes those steps at execution time. Use this when you need to detach reusable steps and stop them from running as part of the test.

Instructions

Remove a shared step reference from a test case. ⚠️ CAUTION: Destructive.

Removes the link to the shared step. The test case will no longer include those steps at execution time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be set to True to proceed with unlinking. Safety measure.
project_idNoOptional override for the default Project ID.
test_case_idYesThe test case to modify.
output_formatNoOutput format: 'json' (default) or 'plain'.
shared_step_idYesThe shared step to unlink.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
stepsNoSerialized scenario steps.
actionNoRequested operation name.
statusNo
test_case_idNo
test_case_urlNo
shared_step_idNo
shared_step_urlNo
requires_confirmationNo
Behavior4/5

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

Annotations already mark destructiveHint true; description reinforces with 'CAUTION: Destructive' and explains effect on execution. Adds context beyond annotations about the runtime impact.

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?

Extremely concise. One sentence plus caution and explanation. Every word contributes; no fluff.

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?

Adequately covers purpose and effect. Does not mention error conditions or prerequisites, but schema is rich and output schema exists. Sufficient for an agent to understand the tool's basic function.

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 additional parameter-level meaning beyond what schema provides.

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?

Clearly states it removes a shared step reference from a test case. The verb 'remove' and resource 'shared step reference' are specific. Distinguishes from siblings like 'link_shared_step' and 'delete_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage: to unlink a shared step from a test case. But no explicit when-to-use or alternatives. Does not compare to similar tools like 'delete_shared_step' or explain when to choose this over other operations.

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