Skip to main content
Glama

quick_review

Capture a screenshot and receive focused design and UX feedback with specific improvement suggestions for rapid visual iteration.

Instructions

Quick design-only review. Captures a screenshot and returns it with a focused design review methodology. No code analysis, no performance audit — just visual/UX feedback. Great for rapid design iteration.

After receiving the screenshot, analyze it as a senior UI designer and provide 5-10 high-impact observations with specific fixes.

This tool is FREE — runs entirely within Claude Code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the page to review

Implementation Reference

  • The 'quick_review' tool is defined, registered, and implemented within 'src/server.ts'. It captures a screenshot using 'captureScreenshot' and returns a design review prompt.
      server.tool(
        "quick_review",
        `Quick design-only review. Captures a screenshot and returns it with a focused design review methodology. No code analysis, no performance audit — just visual/UX feedback. Great for rapid design iteration.
    
    After receiving the screenshot, analyze it as a senior UI designer and provide 5-10 high-impact observations with specific fixes.
    
    This tool is FREE — runs entirely within Claude Code.`,
        {
          url: z.string().url().describe("URL of the page to review"),
        },
        async ({ url }) => {
          try {
            const screenshot = await captureScreenshot({
              url,
              width: 1440,
              height: 900,
              fullPage: true,
              delay: 1000,
              deviceScaleFactor: 2,
            });
    
            return {
              content: [
                {
                  type: "text" as const,
                  text: `# Quick Design Review\n\n**URL:** ${url}\n**Captured:** ${screenshot.timestamp}\n\nScreenshot:`,
                },
                {
                  type: "image" as const,
                  data: screenshot.base64,
                  mimeType: screenshot.mimeType,
                },
                {
                  type: "text" as const,
                  text: [
                    ``,
                    `---`,
                    ``,
                    `# Review Methodology`,
                    ``,
                    QUICK_DESIGN_PROMPT,
                    ``,
                    `---`,
                    ``,
                    `After generating your design review, implement the fixes directly in the code.`,
                  ].join("\n"),
                },
              ],
            };
          } catch (error) {
            const message = error instanceof Error ? error.message : String(error);
            return {
              content: [{ type: "text" as const, text: `Quick review failed: ${message}` }],
              isError: true,
            };
          }
        }
      );
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. It adds valuable execution context ('FREE', 'runs entirely within Claude Code') and discloses the screenshot side effect, but omits safety profile (read-only/destructive), rate limits, or data retention policies that annotations would typically cover.

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?

Generally efficient with three front-loaded sentences. Minor deduction for the second sentence ('After receiving the screenshot...'), which ambiguously blends tool behavior with post-invocation instructions to the AI, potentially confusing the agent about whether the tool performs the analysis or merely supplies the screenshot.

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?

Adequate for a single-parameter tool without output schema. Covers scope, cost, execution environment, and deliverable type (screenshot + methodology). Could improve by clarifying the exact return format or whether the 'design review methodology' is structured data or instructions.

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 has 100% description coverage for the single 'url' parameter. The description does not add syntax details or examples beyond the schema, which is acceptable given the high schema coverage, meeting the baseline expectation.

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?

Excellent specificity: 'Quick design-only review' + 'Captures a screenshot' clearly defines the verb and resource. Explicitly excludes 'code analysis' and 'performance audit,' effectively distinguishing from siblings analyze_code and performance_audit.

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?

Provides clear negative constraints ('No code analysis, no performance audit') defining when NOT to use it, and positive context ('Great for rapid design iteration'). Lacks explicit naming of alternative tools (e.g., 'use performance_audit for speed analysis'), preventing a perfect score.

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/prembobby39-gif/uimax-mcp'

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