Skip to main content
Glama
BauplanLabs

Bauplan MCP Server

Official
by BauplanLabs

delete_tag

Delete a tag from your Bauplan data catalog by providing the tag name. This action removes the specified tag to help keep the catalog organized.

Instructions

Delete a specified tag from the user's Bauplan data catalog using a tag name.

Args: tag: Name of the tag to delete.

Returns: TagDeleted: Object indicating success/failure of the deletion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
deletedYes
tagYes
messageNo
Behavior2/5

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

With no annotations, the description should fully disclose behavior. It only mentions returning a success/failure object, but does not address side effects, permanence, or conditions for failure.

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

Conciseness4/5

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

The description is concise and structured with Args/Returns, every sentence adds value, though it could be more informative.

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?

Missing important context like error handling, what happens if tag doesn't exist, and whether deletion is irreversible, leaving gaps for an AI agent.

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%, and the description only adds that 'tag' is a name, without constraints, format, or examples.

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?

The description clearly states the verb 'Delete' and the resource 'tag', distinguishing it from sibling tools like 'create_tag' and 'has_tag'.

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 on when to use this tool versus alternatives, or prerequisites like the tag must exist before deletion.

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/BauplanLabs/bauplan-mcp-server'

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