Gummble MCP Tools

Gummble currently exposes 14 underscore-delimited tools through tools/list. Their JSON input and output schemas are advertised by the server so compatible clients can validate arguments automatically.

Every tool is marked read-only, non-destructive, and idempotent. Most tools query Gummble's closed library. The two App Store screenshot tools retrieve live public store data and are therefore marked as open-world reads.

These tools research references. They do not modify your project, publish content, send messages, or write to another product.

Discovery and search

Tool	Purpose
`gummble_search_patterns`	Discover broad pattern families such as onboarding, login, checkout, dashboards, and empty states.
`gummble_search_apps`	Find an app by name, brand, keyword, platform, or category.
`gummble_search_screens`	Search real UI screens with natural language and optional platform filtering.
`gummble_search_sections`	Search real marketing-site sections such as hero, pricing, FAQ, features, integrations, and security.
`gummble_search_microcopy`	Search extracted UI copy for UX writing, errors, recovery, paywalls, onboarding, empty states, and buttons.
`gummble_search_flows`	Find complete multi-step journeys instead of isolated screens.
`gummble_find_similar_screens`	Find visually similar screens from a selected `screen_id`.

Detail and comparison

Tool	Purpose
`gummble_get_app`	Fetch one app by slug with metadata, version summaries, and a page of screens.
`gummble_get_screen_detail`	Fetch one screen with a high-fidelity image for visual inspection.
`gummble_get_screen_details_batch`	Fetch metadata for up to six screens and optionally inline selected images.
`gummble_get_flow_screens`	Fetch every ordered screen in one flow.
`gummble_get_flow_screens_batch`	Compare a bounded ordered screen set for several flows in one call; check `structuredContentTruncated` and fetch an individual flow when completeness matters.

App Store marketing screenshots

Tool	Purpose
`gummble_search_store_screenshots`	Search an iOS App Store keyword and return ranked apps with live marketing screenshot URLs.
`gummble_get_store_screenshots`	Fetch the live App Store screenshot set and store metadata for one iOS app.

Recommended workflow

Start with gummble_search_patterns when the design job is broad.
Use a screen, section, flow, or microcopy search for concrete evidence.
Inspect selected references with a screen or flow detail tool.
Use a batch tool when comparing multiple references.
Record layout, hierarchy, states, microcopy, interaction patterns, and source links before proposing an implementation.
Iterate with exclude_ids or gummble_find_similar_screens instead of repeatedly returning the same examples.
Use the store-screenshot tools for App Store marketing work, not in-app UI research.

First bounded request

Call gummble_search_screens once with q "Calendly booking page select a
day and time slot calendar", platform "web", limit 3, and include_images
false. Return the app name and Gummble link for each result, then stop.

Errors

Clients should preserve the server's structured error and recovery guidance. For plan, OAuth, transport, scope, or empty-tool errors, see MCP troubleshooting.