Skip to main content
Glama
amittell

firewalla-mcp-server

by amittell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_target_lists

Read-only

Search and filter Firewalla target lists by name, owner, category, target domains, or note fields to find specific lists for network security management.

Instructions

Search target lists (convenience wrapper with client-side filtering): reads GET /v2/target-lists, sending owner if given (without it, the global and Firewalla-managed lists), and applies the query locally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of target lists to return
ownerNoOnly lists with this owner, sent to the API: "global" (MSP lists), a box gid (that box's lists), or several comma-separated, e.g. "global,<box_gid>". Default: global and Firewalla-managed lists.
queryYesSearch query for target lists. Supported fields: name:*Social*, owner:global/box_gid, category:social/games/ad/porn/etc, targets:*.facebook.com, notes:"description text", target_count:>100 (entries: n, >n, >=n, <n, <=n or a range 10-50), last_updated:>2026-09-01 (a date or Unix seconds, with the same comparisons). Examples: "category:social", "owner:global AND name:*Block*", "targets:*.gaming.com", "target_count:>1000", "last_updated:<2026-01-01"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / category
      Removed value: -{
-  "description": "Filter by category",
-  "type": "string"
-}
    • changedInput schema / properties / owner / description
      Previous value: -"Filter by owner (global or box gid)"New value: +"Only lists with this owner, sent to the API: \"global\" (MSP lists), a box gid (that box's lists), or several comma-separated, e.g. \"global,<box_gid>\". Default: global and Firewalla-managed lists."
    • changedInput schema / properties / query / description
      Previous value: -"Search query for target lists. Supported fields: name:*Social*, owner:global/box_gid, category:social/games/ad/porn/etc, targets:*.facebook.com, notes:\"description text\". Examples: \"category:social\", \"owner:global AND name:*Block*\", \"targets:*.gaming.com\""New value: +"Search query for target lists. Supported fields: name:*Social*, owner:global/box_gid, category:social/games/ad/porn/etc, targets:*.facebook.com, notes:\"description text\", target_count:>100 (entries: n, >n, >=n, <n, <=n or a range 10-50), last_updated:>2026-09-01 (a date or Unix seconds, with the same comparisons). Examples: \"category:social\", \"owner:global AND name:*Block*\", \"targets:*.gaming.com\", \"target_count:>1000\", \"last_updated:<2026-01-01\""
  2. Changed1 schema field changedv1.3.0
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "query"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavior: the query is not sent to the server; filtering happens locally after reading the endpoint, and owner defaults to global and Firewalla-managed lists when omitted. No contradiction with annotations.

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?

A single dense sentence that is front-loaded with the tool's purpose and contains no filler. Every clause contributes behavioral or scoping information, making it easy to extract the key facts quickly.

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

Completeness4/5

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

For a read-only search tool with full schema coverage, the description covers the endpoint, owner default, and local-filtering behavior. It does not describe the return shape, but no output schema exists and the resource name makes the return type predictable; the absence of explicit sibling routing is a minor gap.

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?

Schema coverage is 100%, so the baseline is 3. The description adds one useful semantic beyond the schema: the query is applied client-side while owner is passed through to the API. It does not add detail about limit or query syntax, but the schema already documents those thoroughly.

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?

Clearly identifies the action ('Search') and resource ('target lists') and specifies that it is a convenience wrapper that reads GET /v2/target-lists and applies the query locally. This differentiates it from a direct list call or single-list retrieval without needing to open the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear context: this is a wrapper over GET /v2/target-lists for client-side search/filtering, and the owner parameter controls scope. It does not explicitly name sibling alternatives such as get_target_lists or get_specific_target_list, nor state when not to use it, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools