delete_tag
Remove a tag from OpenMetadata by ID, with options for permanent deletion or cascading removal.
Instructions
Delete a tag from OpenMetadata
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tag_id | Yes | ||
| hard_delete | No | ||
| recursive | No |
Remove a tag from OpenMetadata by ID, with options for permanent deletion or cascading removal.
Delete a tag from OpenMetadata
| Name | Required | Description | Default |
|---|---|---|---|
| tag_id | Yes | ||
| hard_delete | No | ||
| recursive | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description provides no behavioral context beyond 'delete'. It doesn't disclose whether the deletion is permanent, what 'hard_delete' and 'recursive' do, or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
While extremely concise (one sentence), it omits critical information, sacrificing completeness for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 3 parameters, no output schema, and no annotations, the description is severely incomplete, lacking parameter explanations and return value expectations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description adds no meaning to the three parameters (tag_id, hard_delete, recursive). Their behavior remains entirely unspecified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a tag from OpenMetadata' clearly states the action (delete) and the resource (tag), distinguishing it from sibling tools like 'create_tag' and 'delete_tag_category'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like 'delete_tag_category' or 'update_tag'. No criteria for prerequisites or ideal use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yangkyeongmo/mcp-server-openmetadata'
If you have feedback or need assistance with the MCP directory API, please join our Discord server