Skip to main content
Glama
Sign In
awwwards-mcp

awwwards-mcp

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_element

Read-onlyIdempotent

Fetch complete details for one Awwwards element by ID from search results, including title, author, built-with stack, media URLs, related elements, and parent award-winning project.

Instructions

Get one Awwwards element in full: title, author, built-with stack, media URLs, related elements and the parent award-winning project. Use search_elements first for ids.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesElement slug from search_elements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.13.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Addedv1.7.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value the annotations do not: the content of the response (which related entities are joined in), which matters because there is no output schema.

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 short sentences with zero filler. The return payload is front-loaded and the prerequisite follows as an actionable second sentence.

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?

For a one-parameter read with no output schema, the description covers both what comes back and how to obtain the id. It omits what happens on an unknown slug (error vs empty), a minor but real gap for a lookup tool.

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% and the schema already says 'Element slug from search_elements', which the description's 'Use search_elements first for ids' largely restates. Minor added emphasis on where to source the id, but no format or failure-mode detail beyond the schema.

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 one Awwwards element') and enumerates exactly what 'in full' returns: title, author, stack, media URLs, related elements, parent project. This distinguishes it from search_elements (bulk lookup) and get_site_elements (site-scoped) without needing the schemas.

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?

Explicitly names the prerequisite workflow: 'Use search_elements first for ids', routing the agent to the right sibling to obtain the required slug. No explicit when-not-to-use condition, but for a single-record fetch the alternative is already named.

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