Skip to main content
Glama
intruder-io

intruder-mcp

Official

delete_target_tag

Remove a specific tag from a target in Intruder.IO to organize and manage security testing assets.

Instructions

    Remove a tag from a target.

    Args:
        target_id: The ID of the target to remove the tag from
        tag_name: The name of the tag to remove
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_idYes
tag_nameYes

Implementation Reference

  • MCP tool handler decorated with @mcp.tool(). Implements the delete_target_tag tool by calling the API client method and returning a success message. This is both the handler and registration point.
    @mcp.tool()
    async def delete_target_tag(target_id: int, tag_name: str) -> str:
        """
        Remove a tag from a target.
    
        Args:
            target_id: The ID of the target to remove the tag from
            tag_name: The name of the tag to remove
        """
        api.delete_target_tag(target_id=target_id, tag_name=tag_name)
        return f"Removed tag '{tag_name}' from target {target_id}"
  • Helper method in API client class that executes the actual HTTP DELETE request to remove the specified tag from the target.
    def delete_target_tag(self, target_id: int, tag_name: str) -> None:
        self.client.delete(f"{self.base_url}/targets/{target_id}/tags/{tag_name}/")
Behavior2/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 behavioral disclosure. It states the action ('Remove') but doesn't specify if this is destructive, requires specific permissions, has side effects (e.g., affecting related data), or what happens on success/failure. This is inadequate for a mutation tool with zero 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.

Conciseness4/5

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

The description is front-loaded with the core purpose in the first sentence, followed by parameter details. It's efficient with minimal waste, though the parameter explanations are somewhat terse and could be more integrated into the flow.

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?

Given the complexity of a mutation tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It fails to address critical aspects like error conditions, return values, or behavioral nuances, making it insufficient for safe and effective tool invocation.

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?

The description adds basic semantics by naming the parameters ('target_id' and 'tag_name') and briefly explaining their roles, which compensates for the 0% schema description coverage. However, it doesn't provide details like format constraints or examples, leaving gaps in understanding.

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

Purpose4/5

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

The description clearly states the action ('Remove') and the target resource ('a tag from a target'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_target' or 'snooze_issue', which would be needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'delete_target' or 'create_target_tag'. It lacks context about prerequisites, such as whether the tag must exist or if the target must be in a specific state, leaving the agent without usage direction.

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/intruder-io/intruder-mcp'

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