Skip to main content
Glama

Search Iconfont Icons

iconfont_search_icons
Read-onlyIdempotent

Search millions of icons from Iconfont.cn by name and style, with pagination and output format options.

Instructions

Search for icons in the Iconfont icon library (iconfont.cn).

This tool searches the Iconfont database for icons matching the specified query. It provides access to millions of icons from various designers and collections.

Args:

  • query (string, required): Search query for icon name

  • icon_type (string, optional): Icon style type - '' for all, 'line' for outline, 'fill' for filled, 'flat' for flat, 'hand' for hand-drawn, 'simple' for simple, 'complex' for elaborate (default: all)

  • page (number, optional): Page number for pagination, starting from 1 (default: 1)

  • page_size (number, optional): Number of results per page, max 100 (default: 54)

  • response_format ('markdown' | 'json', optional): Output format (default: markdown)

Returns: For JSON format: { total: number, page: number, page_size: number, icons: [...] } For markdown: Human-readable list with icon names and IDs

Examples:

  • Use when: "Find home icons" -> query="home"

  • Use when: "Search outline-style arrows" -> query="arrow", icon_type="line"

  • Use when: "Get page 2 of search results" -> query="user", page=2

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for icon name
icon_typeNoIcon style type: empty for all, 'line' for outline, 'fill' for filled, 'flat' for flat, 'hand' for hand-drawn, 'simple' for simple, 'complex' for elaborate
pageNoPage number for pagination
page_sizeNoNumber of results per page (max 100)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds valuable context beyond annotations by specifying the data source ('Iconfont database'), scale ('millions of icons'), and output format details (JSON structure vs markdown presentation). It doesn't mention rate limits or authentication requirements, but annotations provide openWorldHint=true, so this is reasonably complete.

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 well-structured with clear sections (overview, Args, Returns, Examples) and front-loads the core purpose. Some redundancy exists between the Args section and schema descriptions, but the examples add practical value. The text is appropriately sized for a tool with 5 parameters and no output schema.

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 moderate complexity (search operation with pagination and format options), rich annotations (covering safety and idempotency), and 100% schema coverage, the description provides excellent contextual completeness. It explains what the tool does, when to use it, parameter usage through examples, and output format differences, making it fully self-contained for an AI agent.

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 100%, so the schema already fully documents all parameters. The description repeats parameter information in the Args section but adds minimal extra context (e.g., 'max 100' for page_size is already in schema). It provides helpful examples showing parameter usage, but doesn't add significant semantic value beyond what's in the structured schema.

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 specific action ('search for icons'), target resource ('Iconfont icon library'), and scope ('millions of icons from various designers and collections'). It distinguishes itself from siblings like iconfont_download_icon (download) and iconfont_project_search_icons (project-specific search) by focusing on general icon search across the entire library.

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

Usage Guidelines5/5

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

The description provides explicit usage examples with specific scenarios ('Find home icons', 'Search outline-style arrows', 'Get page 2 of search results'), effectively demonstrating when to use this tool. It also implicitly distinguishes from siblings by not mentioning project-specific searches or download operations, guiding users toward the appropriate tool for general icon discovery.

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/GuoChen-thlg/iconfont-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server