Skip to main content
Glama
YonasValentin

Design Inspiration MCP Server

Search design references

design_search_references
Read-onlyIdempotent

Search design platforms like Dribbble and Behance for UI inspiration, case studies, and design system documentation to inform your creative projects.

Instructions

Web search scoped to design platforms. Returns article titles, snippets, and links. Better than image search when you want case studies, write-ups, or design system documentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesUI design search query. Examples: "best dashboard designs 2025", "mobile navigation patterns"
sitesNoFilter to specific design sites. Empty array searches all sites.
numNoNumber of results to return (1-20, default: 10)

Implementation Reference

  • The handler function for the `design_search_references` tool which performs the web search using `serperRequest` and formats the output.
    }, async (params: SearchReferencesInput) => {
      try {
        const siteQuery = buildSiteQuery(params.query, params.sites);
        const data = await serperRequest<SerperSearchResponse>("/search", {
          q: siteQuery,
          num: params.num,
        });
    
        const results = data.organic || [];
        const text = formatSearchResults(results, params.query);
    
        return {
          content: [{ type: "text" as const, text }],
          structuredContent: {
            query: params.query,
            count: results.length,
            results: results.map((r) => ({
              title: r.title,
              link: r.link,
              snippet: r.snippet,
              position: r.position,
            })),
          },
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: error instanceof Error ? error.message : `Error: ${String(error)}`,
            },
          ],
        };
  • src/index.ts:236-245 (registration)
    Registration of the `design_search_references` tool with its title, description, schema, and annotations.
    server.registerTool("design_search_references", {
      title: "Search design references",
      description: `Web search scoped to design platforms. Returns article titles, snippets, and links. Better than image search when you want case studies, write-ups, or design system documentation.`,
      inputSchema: SearchReferencesInputSchema,
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
Behavior4/5

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

Annotations cover read-only, open-world, idempotent, and non-destructive traits, so the description doesn't need to repeat these. It adds valuable context by specifying the search scope ('design platforms') and the types of content returned ('article titles, snippets, and links'), which helps the agent understand the tool's behavior beyond the annotations. No contradictions with annotations are present.

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?

The description is front-loaded with the core purpose in the first sentence, followed by a clarifying second sentence on usage guidelines. Both sentences are essential, with no wasted words, making it efficient and well-structured for quick comprehension.

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?

Given the tool's moderate complexity (3 parameters, 100% schema coverage, no output schema), the description is largely complete. It covers purpose, usage guidelines, and behavioral context, though it could slightly enhance completeness by mentioning the lack of output schema or potential limitations like result freshness. However, it provides sufficient context for effective use.

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%, with each parameter well-documented in the schema (e.g., query examples, site options, result limits). The description does not add significant semantic details beyond the schema, such as explaining parameter interactions or edge cases. Baseline score of 3 is appropriate as the schema carries the full burden.

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?

The description clearly states the tool performs a 'web search scoped to design platforms' and specifies it 'returns article titles, snippets, and links.' It distinguishes from sibling tools like 'design_search_images' by emphasizing it's 'better than image search when you want case studies, write-ups, or design system documentation,' making the purpose specific and differentiated.

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?

The description provides explicit guidance on when to use this tool versus alternatives: it states it's 'better than image search when you want case studies, write-ups, or design system documentation,' which implicitly contrasts with sibling tools like 'design_search_images' and 'design_search_styles.' This gives clear context for selection among similar tools.

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/YonasValentin/design-inspiration-mcp-server'

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