Skip to main content
Glama
intruder-io

intruder-mcp

Official

list_tags

Retrieve all tags from your Intruder account to organize and filter targets, with optional filtering by target address.

Instructions

    List all tags in the Intruder account with optional filters. Tags are applied to targets.

    Args:
        target_address: Filter by a list of target address
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_addressNo

Implementation Reference

  • The handler function for the 'list_tags' tool. It is registered as an MCP tool using the @mcp.tool() decorator. Fetches all targets (optionally filtered by address) using the IntruderAPI, collects unique tags from them, sorts them, and returns as a newline-separated string.
    @mcp.tool()
    async def list_tags(target_address: Optional[str] = None) -> str:
        """
        List all tags in the Intruder account with optional filters. Tags are applied to targets.
    
        Args:
            target_address: Filter by a list of target address
        """
        targets = api.list_targets_all(address=target_address)
        tags = set()
        for target in targets:
            if target.tags:
                tags.update(target.tags)
        return "\n".join(sorted(tags))
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions filtering capability but lacks details on permissions required, rate limits, pagination, or the format of returned data. For a list operation with no annotation coverage, this leaves significant behavioral gaps.

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 sized with two sentences and an Args section. It is front-loaded with the main purpose, but the Args formatting could be more integrated. There is no wasted text, though it could be slightly more polished.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It covers basic purpose and one parameter but misses critical details like return format, error handling, and full behavioral context needed for effective tool use.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'target_address' filters by a list of target addresses, which clarifies the parameter's purpose beyond the schema's title. However, it does not detail the format (e.g., comma-separated list) or constraints, leaving some ambiguity.

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 verb ('List') and resource ('all tags in the Intruder account'), and explains what tags are ('applied to targets'). However, it does not explicitly differentiate from sibling tools like 'list_targets' or 'list_issues', which reduces it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through 'optional filters' and the example of filtering by target address, but does not provide explicit guidance on when to use this tool versus alternatives like 'list_targets' or 'create_target_tag'. No exclusions or prerequisites are mentioned.

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