Skip to main content
Glama
Sign In

Icons8

by com.icons8
OverviewDiscussionsAdmin

Get icon PNG link

get_icon_png_url
Read-only

Get a PNG URL for an icon by its ID - use when SVG is not available. NOTE: SVG format is preferred for Icons8 icons when possible (use get_icon_svg).

An animated icon's PNG is a still frame. Use get_icon_animation for the motion.

Args: icon_id: The id from a search_icons result (field icons[].id) ctx: MCP context for API access size: The preview image size in pixels (default: 24)

Returns: Dictionary containing the PNG preview URL

Input Schema

NameRequiredDescriptionDefault
sizeNo
icon_idYesIcon id from the results of search_icons (field icons[].id)

Output Schema

NameRequiredDescriptionDefault
urlYesPermanent PNG link of the icon at the asked size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / icon_id / description
      Added value: +"Icon id from the results of search_icons (field icons[].id)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "url": {
+      "description": "Permanent PNG link of the icon at the asked size.",
+      "title": "Url",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url"
+  ],
+  "title": "IconPngUrlResult",
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds one genuinely useful behavioral caveat ('An animated icon's PNG is a still frame'), but does not disclose URL permanence, auth needs, or any other runtime behavior beyond that single note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core guidance is front-loaded and useful, but the 'Args:' and especially 'Returns:' block duplicate information already present in the input and output schemas, and the 'ctx' arg is an internal detail that does not belong in an agent-facing description. Some trimming would sharpen it.

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?

With annotations covering the safety profile and an output schema covering return values, the description's job is to add selection and caveat context, which it does well. It is essentially complete for a simple URL-fetch tool; only minor details like URL lifetime are absent.

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 description coverage is only 50% (icon_id documented, size not), so the description must compensate. It does: it explains size as 'The preview image size in pixels (default: 24)' and restates the icon_id source. Minor noise from mentioning 'ctx' as an argument that is not in the schema keeps this below a 5.

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?

States a specific verb and resource ('Get a PNG URL for an icon by its ID') and immediately distinguishes itself from siblings by naming get_icon_svg as the preferred format and get_icon_animation for motion. An agent can select this tool without opening any schema.

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?

Explicitly states when to use ('use when SVG is not available'), when not to ('SVG format is preferred ... use get_icon_svg'), and the alternative for animated content ('Use get_icon_animation for the motion'). Nothing is left to inference.

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

All Icons8 toolsInspect
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.

Resources