Skip to main content
Glama
intruder-io

intruder-mcp

Official

delete_target_tag

Remove a tag from a target by specifying the target ID and tag name.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function that implements 'delete_target_tag'. It receives target_id and tag_name, calls the API client, and returns a confirmation string.
    @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}"
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on line 236.
    @mcp.tool()
    async def delete_target_tag(target_id: int, tag_name: str) -> str:
  • The API client helper method that sends the actual HTTP DELETE request to the Intruder API to remove a tag from a 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}/")
Behavior3/5

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

With no annotations, the description carries full burden. It states 'Remove a tag' implying mutation but omits details like idempotency, error conditions, or permissions.

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-line purpose plus docstring for params. No wasted text; easy to parse.

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

Completeness3/5

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

Adequate for a simple mutation but missing usage context (e.g., whether tag must exist, interactions with sibling tools). Output schema exists but description doesn't need to cover return values.

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

Parameters4/5

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

The description includes docstrings for both target_id and tag_name, providing meaning beyond the schema's titles and types. This compensates for the 0% schema description coverage.

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 action ('Remove a tag from a target') using specific verb and resource, distinguishing it from siblings like create_target_tag and delete_target.

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 vs alternatives (e.g., delete_target). Lacks context about prerequisites such as the tag or target existence.

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