Skip to main content
Glama
intruder-io

intruder-mcp

Official

delete_target

Remove a target from Intruder.IO by specifying its ID. This action permanently deletes the selected target from the security testing platform.

Instructions

    Delete a target.

    Args:
        target_id: The ID of the target to delete
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_idYes

Implementation Reference

  • The MCP tool handler for 'delete_target', registered via @mcp.tool() decorator. It calls the API client to delete the target by ID and returns a confirmation message.
    @mcp.tool()
    async def delete_target(target_id: str) -> str:
        """
        Delete a target.
    
        Args:
            target_id: The ID of the target to delete
        """
        api.delete_target(target_id)
        return f"Deleted target {target_id}"
  • Supporting method in IntruderAPI class that sends HTTP DELETE request to the Intruder API to delete the specified target.
    def delete_target(self, target_id: str) -> None:
        self.client.delete(f"{self.base_url}/targets/{target_id}/")
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 but only states the action ('Delete') without detailing consequences (e.g., permanent vs. reversible, impact on related data), permissions required, or error conditions. This is inadequate for a destructive operation, leaving critical behavioral traits unspecified.

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 appropriately concise with two sentences: a purpose statement and a parameter explanation. It's front-loaded with the main action, though the parameter details could be integrated more seamlessly. There's no wasted text, making it efficient in structure despite content gaps.

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 tool's destructive nature, lack of annotations, no output schema, and minimal parameter guidance, the description is incomplete. It fails to address critical aspects like return values, error handling, or safety warnings, leaving the agent under-informed for a high-stakes operation in a context with multiple sibling tools.

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 minimal semantics by naming 'target_id' as 'The ID of the target to delete', which clarifies the parameter's role but doesn't provide format examples, validation rules, or sourcing guidance. With 0% schema description coverage and only one parameter, this offers basic compensation, aligning with the baseline for low coverage but limited enhancement.

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

Purpose2/5

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

The description 'Delete a target' is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what a 'target' represents in this context or distinguish this tool from sibling tools like 'delete_target_tag' or 'cancel_scan', leaving the purpose vague beyond the basic verb-noun pairing.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., target existence), exclusions (e.g., cannot delete if in use), or relationships to sibling tools like 'list_targets' for selection or 'create_targets' for reversal, offering minimal context for decision-making.

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