Skip to main content
Glama
INSANE0777

awwwards-mcp

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_sites

Read-only

Search award-winning websites on Awwwards by text, tags, award, color, or technology. Returns site cards with screenshots, live URLs, awards, and tags.

Instructions

Search award-winning websites on Awwwards. Returns site cards with inline screenshots, live URLs, awards and tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
tagsNoTag slugs, e.g. ['3d', 'portfolio']
awardNo
colorNoDominant color hex, e.g. '#404040'
countNo
queryNoFree text matched against site titles and tags
sortByNoSort results: by Awwwards jury score (details previously fetched) or newest firstnewest
technologyNoTechnology slug, e.g. 'webgl', 'gsap', 'astro'
responseModeNofull (default) returns all inline previews; compact returns concise cards and at most two page previewsfull

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.2
    • addedInput schema / properties / responseMode
      Added value: +{
+  "default": "full",
+  "description": "full (default) returns all inline previews; compact returns concise cards and at most two page previews",
+  "enum": [
+    "full",
+    "compact"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the read-only, non-destructive safety profile, so the bar is lower. The description adds useful behavioral value by describing the return shape (site cards with inline screenshots, live URLs, awards, tags), but says nothing about pagination, result limits, or the effect of responseMode on payload size.

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?

Two sentences, no filler, with the primary action stated first and the return contents immediately after. Nothing in it can be cut without losing information.

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?

With no output schema, describing the card contents is necessary and present, which helps. However, a 9-parameter search tool with no usage scoping and undocumented pagination/count behavior is only minimally covered.

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

Parameters2/5

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

Across 9 parameters the description adds no filtering semantics at all: it only mentions tags and awards as things returned in cards, not as query filters. With 67% schema coverage, page, award, and count have no documented meaning in either place, so the description fails to compensate for the gap.

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?

Specific verb+resource ('Search award-winning websites on Awwwards') with the return payload named, so the agent can tell it is a query tool rather than a detail/fetch tool. It does not explicitly contrast itself with siblings like search_elements, new_winners, or get_site_details.

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?

No when-to-use guidance, no prerequisites, and no named alternatives. The agent must infer from the name that this is the entry point before drilling into get_site_details or compare_sites.

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

Deploy Server

Other Tools