easysociable-mcp

Search icons

search_icons

Read-onlyIdempotent

Search a curated icon catalog by keyword, collection, or visual style to find icons for template design and decorations. Choose from up to 8 candidates before generating assets.

Instructions

Search the internal safe Template Icon Catalog (curated Iconify collections) by keyword, collection, or visual style. Use when designing templates or adding icon decorations. Select ≤8 candidates and confirm choice before materializing. Alternatives: Call get_icon once an iconId is selected to generate the immutable asset. Read-only catalog search; does not consume quota.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max number of candidates to return (default 8; prefer small limits for token budget).
`query`	Yes	Search term for icon meaning or keyword (e.g. arrow, checkmark, star).
`style`	No	Icon rendering style: outline \| solid \| any
`collection`	No	Optional icon collection filter (e.g. lucide, tabler).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`icons`	No	Candidate icons array with id, name, and previewSvg.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "icons": {
+      "description": "Candidate icons array with id, name, and previewSvg.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedv0.1.16Oct 5, 2026

addedInput schema / properties / collection / description

Added value: +"Optional icon collection filter (e.g. lucide, tabler)."

addedInput schema / properties / limit / description

Added value: +"Max number of candidates to return (default 8; prefer small limits for token budget)."

addedInput schema / properties / query / description

Added value: +"Search term for icon meaning or keyword (e.g. arrow, checkmark, star)."

changedInput schema / properties / style / description

Previous value: -"outline | solid | any"New value: +"Icon rendering style: outline | solid | any"

First observedv0.1.13Oct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered; the description nonetheless adds non-obvious operational context: it does not consume quota and that candidates must be confirmed before materializing an asset. It does not discuss rate limits or result ordering, so it falls short of a 5.

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?

Purpose is front-loaded and the sentences are short and purposeful. There is mild redundancy between the description and the schema/annotations (read-only, the ≤8 limit which the limit default already implies), which keeps it from a 5.

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?

With an output schema present, return values need no explanation; the description covers the remaining agent-relevant gaps — search scope, the get_icon handoff, quota impact and the confirmation step before materializing. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the schema already documents query, limit, style and collection, including the token-budget guidance on limit. The description only restates the search axes, adding no syntax, defaults or format detail beyond the schema, so the baseline 3 applies.

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 (search) plus resource (Template Icon Catalog / curated Iconify collections) and the three axes of search (keyword, collection, visual style). It also names the follow-up sibling get_icon, so an agent can place it in the workflow without opening another 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?

Explicit when-to-use (designing templates, adding icon decorations), an explicit alternative with its trigger condition (get_icon once an iconId is selected), and a workflow constraint (select ≤8 candidates and confirm before materializing). Nothing about selection 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.