iconify

Search Icons

search_icons

Read-onlyIdempotent

Search for icons by keyword across all collections. Returns icon names in prefix:name format (e.g., "mdi:home"). Use get_icons to fetch SVG data for results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (1-999, default 32)
`query`	Yes	Search keyword (e.g., "home", "arrow", "user")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`icons`	Yes	Icon names in prefix:name format (e.g., mdi:home)
`total`	Yes	Total number of matching icons across all collections

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "icons": {
+      "description": "Icon names in prefix:name format (e.g., mdi:home)",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of matching icons across all collections",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "icons"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "home"
+  },
+  {
+    "limit": 50,
+    "query": "arrow"
+  }
+]

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds value by disclosing the output format and that it returns names only, not SVG data, which is beyond annotation information.

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?

The description is two concise sentences, front-loaded with the purpose and then providing the output format and pointer to get_icons. No unnecessary words or repetition.

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

Completeness5/5

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

Given the tool's simplicity, full schema, output schema, and strong annotations, the description is complete. It covers purpose, output format, and the next step (get_icons), so no critical gaps remain.

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 input schema has 100% coverage with descriptions and examples for both query and limit. The description itself does not add parameter-specific details, so the baseline score of 3 is appropriate.

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 tool searches for icons by keyword across all collections, which is specific and distinguishing. It also mentions the output format (prefix:name), further clarifying its purpose relative to get_icons.

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 explicitly directs users to use get_icons to fetch SVG data, indicating when to use this tool as a search step. It provides clear context for when this tool is appropriate, though it lacks an explicit when-not-to-use statement for other scenarios.

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

All iconify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.