Skip to main content
Glama

search_icons

Search and filter icons from Freepik's library by term, slug, family, color, shape, and other criteria to find visual assets for projects.

Instructions

Get a list of icons based on the provided parameters and ordering criteria.

Query Parameters:

  • term: Search term. If only term comes, it is searched for term, if only slug comes, it is searched for slug and if both come, it is searched for slug

  • slug: Search by slug

  • page: Page number. It must be greater than 0.

  • per_page: Results per page. It must be greater than 0.

  • family-id: Icon family id.

  • order: Define order of results.

  • Note: If the term or slug parameter is used, the order will be the similarity of the search.

  • thumbnail_size: Size of the thumbnail. If the size is not specified, the API will return 128 as a default size.

  • filters: Filter parameters for icons

Responses:

  • 200 (Success): OK Response

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "data": [
    {
      "free_svg": true,
      "created": "2023-03-07T23:05:26Z",
      "author": {
        "assets": 0,
        "name": "John Doe",
        "id": 2147483647,
        "avatar": "https://avatar.cdnpk.net/61668527-220726032514.jpg",
        "slug": "merry-christmas"
      },
      "name": "a woman reads a book in a tablet sits in the luxurious back of the library",
      "style": {
        "name": "Meticulous Yellow shadow",
        "id": 50
      },
      "id": 52912,
      "family": {
        "total": 1200,
        "name": "Outline",
        "id": 1
      },
      "thumbnails": [
        {
          "width": 512,
          "url": "https://v4.cdnpk.net/videvo_files/video/free/video0485/thumbnails/_import_61a866e2519c71.61070863_large.png",
          "height": 512
        },
        {
          "width": 512,
          "url": "https://v4.cdnpk.net/videvo_files/video/free/video0485/thumbnails/_import_61a866e2519c71.61070863_large.png",
          "height": 512
        }
      ],
      "slug": "a-woman-reads-a-book-in-a-tablet-sits-in-the-luxurious-back-of-the-library",
      "tags": [
        {
          "name": "Dog",
          "slug": "dog"
        },
        {
          "name": "Dog",
          "slug": "dog"
        }
      ]
    },
    {
      "free_svg": true,
      "created": "2023-03-07T23:05:26Z",
      "author": {
        "assets": 0,
        "name": "John Doe",
        "id": 2147483647,
        "avatar": "https://avatar.cdnpk.net/61668527-220726032514.jpg",
        "slug": "merry-christmas"
      },
      "name": "a woman reads a book in a tablet sits in the luxurious back of the library",
      "style": {
        "name": "Meticulous Yellow shadow",
        "id": 50
      },
      "id": 52912,
      "family": {
        "total": 1200,
        "name": "Outline",
        "id": 1
      },
      "thumbnails": [
        {
          "width": 512,
          "url": "https://v4.cdnpk.net/videvo_files/video/free/video0485/thumbnails/_import_61a866e2519c71.61070863_large.png",
          "height": 512
        },
        {
          "width": 512,
          "url": "https://v4.cdnpk.net/videvo_files/video/free/video0485/thumbnails/_import_61a866e2519c71.61070863_large.png",
          "height": 512
        }
      ],
      "slug": "a-woman-reads-a-book-in-a-tablet-sits-in-the-luxurious-back-of-the-library",
      "tags": [
        {
          "name": "Dog",
          "slug": "dog"
        },
        {
          "name": "Dog",
          "slug": "dog"
        }
      ]
    }
  ],
  "meta": {
    "pagination": {
      "per_page": 1,
      "total": 1,
      "last_page": 1,
      "current_page": 1
    }
  }
}
  • 400: Bad Request - The server could not understand the request due to invalid syntax.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 401: Unauthorized - The client must authenticate itself to get the requested response.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 404: Not Found - The server can not find the requested resource.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 500: Internal Server Error - The server has encountered a situation it doesn't know how to handle.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "Internal Server Error"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
Accept-LanguageNoSpecifies the search query language using the ISO 639-1 (2-letter language code) and the ISO 3166-1 (2-letter country code) for language variants. The API will use "en-US" as a default language for processing if a code is not provided, or does not exist.
termNoSearch term. If only term comes, it is searched for term, if only slug comes, it is searched for slug and if both come, it is searched for slug
slugNoSearch by slug
pageNoPage number. It must be greater than 0.
per_pageNoResults per page. It must be greater than 0.
family-idNoIcon family id.
orderNoDefine order of results. - Note: If the term or slug parameter is used, the order will be the similarity of the search. relevance
thumbnail_sizeNoSize of the thumbnail. If the size is not specified, the API will return 128 as a default size.
filtersNoFilter parameters for icons
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds some context: it describes pagination behavior (via 'page' and 'per_page'), default values (e.g., 'thumbnail_size' defaults to 128), and search logic (e.g., term/slug interactions). However, it lacks details on rate limits, authentication needs, or error handling beyond HTTP codes, leaving gaps for a tool with 9 parameters.

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

Conciseness2/5

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

The description is overly verbose and poorly structured. It front-loads the purpose but then duplicates schema details and includes extensive, repetitive JSON examples for responses. The 'Query Parameters' and 'Responses' sections add bulk without significant new information, making it inefficient and hard to scan.

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

Completeness3/5

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

Given the tool's complexity (9 parameters, nested objects) and lack of annotations or output schema, the description is moderately complete. It covers basic functionality, parameters, and response formats with examples, but it misses behavioral aspects like authentication requirements or rate limits. The inclusion of HTTP response details helps, but it's not fully compensatory for the missing structured data.

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 documents all parameters thoroughly. The description repeats parameter information in the 'Query Parameters' section, adding minimal value beyond the schema. It does clarify interactions (e.g., term/slug search logic) and defaults, but this is largely redundant with the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get a list of icons based on the provided parameters and ordering criteria.' It specifies the verb ('Get') and resource ('icons'), and distinguishes it from siblings like 'download_icon_by_id' or 'get_icon_detail_by_id' by focusing on search/list functionality. However, it doesn't explicitly differentiate from 'search_resources' (a sibling tool), which might cause ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'search_resources' (which might overlap) or 'get_icon_detail_by_id' (for single icons), nor does it specify prerequisites or exclusions. Usage is implied through the description of parameters but lacks explicit context.

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/freepik-company/freepik-mcp'

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