Skip to main content
Glama

Search Icons in Iconfont Project

iconfont_project_search_icons
Read-onlyIdempotent

Search for icons within a specific Iconfont project using keywords to find relevant icons quickly. Requires project ID and authentication.

Instructions

Search for icons within a specific Iconfont project using keyword.

This tool searches icons inside a specific project that the user has access to. Requires authentication via Iconfont cookie.

Args:

  • cookie (string, optional): The EGG_SESS_ICONFONT cookie from iconfont.cn. Can be used instead of setting environment variable.

  • pid (string, required): Project ID (can be obtained from iconfont_list_projects)

  • keyword (string, required): Keyword to search for icons within the project

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

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

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

Note: Requires authentication. Can provide cookie via args, ICONFONT_COOKIE environment variable, or iconfont_login tool.

Examples:

  • Use when: "Search copy icons in project 1997925" -> pid="1997925", keyword="copy"

  • Use when: "Search text formatting icons in my project" -> pid="123456", keyword="text"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cookieNoThe EGG_SESS_ICONFONT cookie from iconfont.cn. Can be used instead of setting environment variable.
pidYesProject ID (can be obtained from iconfont_list_projects)
keywordYesKeyword to search for icons within the project
pageNoPage number for pagination
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?

The description adds valuable behavioral context beyond what annotations provide: it explains authentication requirements (cookie, environment variable, or login tool), describes pagination behavior, and specifies output formats. While annotations cover safety (readOnly, non-destructive), the description provides practical implementation details that help the agent use the tool correctly.

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 (purpose, authentication, args, returns, notes, examples). While slightly longer than minimal, every sentence adds value. The information is front-loaded with the core purpose first.

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?

For a search tool with comprehensive annotations and full parameter documentation, the description provides excellent contextual completeness. It covers authentication methods, output formats, practical examples, and distinguishes from siblings. The lack of output schema is compensated by clear return format descriptions.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal additional semantic context - mainly reinforcing that 'pid' can be obtained from another tool and providing usage examples. This meets the baseline for high schema coverage.

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'), resource ('within a specific Iconfont project'), and scope ('using keyword'). It distinguishes this tool from the sibling 'iconfont_search_icons' by specifying it searches within a specific project rather than globally.

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 guidance on when to use this tool with concrete examples ('Search copy icons in project 1997925'), mentions authentication requirements, and distinguishes it from the global search sibling. The 'Examples' section gives clear usage scenarios.

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