Skip to main content
Glama

Download Iconfont Icon SVG

iconfont_download_icon
Idempotent

Download SVG content for an icon from Iconfont using its icon ID. Optionally save the SVG to a file or provide a project ID for private icons.

Instructions

Download SVG data for a specific icon from Iconfont.

This tool retrieves the SVG content for an icon and optionally saves it to a file. The icon_id can be obtained from the search results. For icons in private projects, you must provide the project_id parameter.

Args:

  • icon_id (string, required): The icon ID to download (from search results)

  • project_id (string, optional): Project ID for private project icons (from iconfont_list_projects)

  • output_path (string, optional): Directory path to save the SVG file

  • filename (string, optional): Filename for the downloaded SVG (without extension)

Returns: For JSON format: { icon_id: string, name: string, svg: string, saved_to: string | null } For markdown: Confirmation message with file path if saved

Examples:

  • Use when: "Download the home icon" -> icon_id from search results

  • Use when: "Download from a private project" -> icon_id, project_id

  • Use when: "Save to specific folder" -> output_path="./src/icons"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icon_idYesThe icon ID to download (from search results)
project_idNoProject ID (required for icons in private projects; can be obtained from iconfont_list_projects)
output_pathNoDirectory path to save the SVG file (defaults to current directory)
filenameNoFilename for the downloaded SVG (without extension)
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 indicate idempotentHint=true but no readOnly or destructive hints. The description explains it retrieves SVG and optionally saves to file, which is consistent with mutable but non-destructive behavior. It does not detail potential overwrite scenarios, but the idempotent hint mitigates that.

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?

Description is well-structured with intro, args list, returns, and examples. Every section is concise and adds value, with the main purpose stated upfront. No unnecessary fluff.

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?

Despite not having an output schema, the description explains return formats (JSON vs Markdown) and provides usage examples. It covers all parameters and gives clear instructions on parameter dependencies, making it complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds valuable context: icon_id from search, project_id from list_projects, output_path defaults to current directory, filename without extension. The returns section also clarifies output formats, enhancing schema information.

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?

Title 'Download Iconfont Icon SVG' and description 'Download SVG data for a specific icon from Iconfont' clearly state the verb (download) and resource (SVG for an icon). The description also specifies optional file saving, distinguishing it from sibling search/list tools.

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?

Examples provide specific use cases (download icon, from private project, to specific folder) and mention how to obtain icon_id from search results and project_id from iconfont_list_projects. However, it does not explicitly state when not to use this tool versus siblings, though the context implies it.

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