Ravelry MCP Server

Search Ravelry patterns

search_patterns

Read-onlyIdempotent

Search Ravelry patterns by keyword and filters like craft, yarn weight, yardage, difficulty, fit, and techniques to find matching knitting and crochet designs.

Instructions

Search the Ravelry pattern database by keyword and filters: craft, category, yarn weight, yardage, difficulty, fit, techniques and construction (attributes), language, designer and price. Returns a page of matches; call get_pattern_details with the ids for yarn, gauge, needles and notes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fit`	No	Who it is sized for, or how it fits: "petite", "plus", "tall", "maternity", "negative-ease", "oversized"... (any of them matches).
`page`	No	1-based results page.
`sort`	No	Result order. Defaults to Ravelry's "best match".
`craft`	No	Only return patterns for this craft. Omit for all crafts.
`query`	No	Free-text search, e.g. "cabled beanie". Omit to browse by filters alone.
`weight`	No	Yarn weights the pattern is written for (any of them matches).
`category`	No	What the pattern makes, in plain words: "hat", "socks", "cardigan", "shawl", "blanket", "toy"... The closest Ravelry category is used.
`designer`	No	Only patterns by this designer, e.g. "Ysolda Teague".
`language`	No	Language the pattern is written in, as a code: en, fr, de, es, ja, nl...
`page_size`	No	Results per page (max 50).
`attributes`	No	Techniques and construction, in plain words: "top down", "seamless", "raglan", "cables", "stranded", "lace", "brioche", "toe up", "heel flap", "granny square", "tunisian", "chart", "written", "video tutorial", "Fair Isle", "v neck", "pockets"... Mapped to Ravelry pattern attributes.
`yardage_max`	No	Maximum total yardage, in yards (1 m ≈ 1.09 yd). Use for "what can I make with the yarn I have".
`yardage_min`	No	Minimum total yardage, in yards.
`availability`	No	free = free patterns only (default); ravelry = sold as a Ravelry download; online = available on another website; inprint = in a printed book/magazine; any = no filter.	free
`difficulty_max`	No	Highest average difficulty rating, 1 (easiest) to 10. Beginner ≈ 3 or less.
`attribute_match`	No	Whether patterns need all the attributes (default) or any of them.	all

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes
`units`	No	The signed-in user's units.
`category`	Yes	The Ravelry category the search was filtered to.
`patterns`	Yes
`attributes`	Yes	The Ravelry attributes the search was filtered to, by name.
`page_count`	Yes
`total_results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Oct 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the safety profile is covered. The description adds genuine workflow context by describing the paginated result shape and the two-step search-then-detail pattern, though it says nothing about rate limits or result caps beyond the schema's page_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, front-loaded with the core action and ending with the actionable next step. The filter enumeration is dense but earns its place by previewing the filter surface.

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?

An output schema exists, so return values need not be re-explained, and the description covers scope plus the follow-up call. For a 16-parameter tool the description is adequate, though it could note pagination behavior more explicitly.

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% and every parameter is documented in-schema with enums and defaults, so the schema carries the semantics. The description's filter list largely restates those schema fields without adding syntax or format detail, matching the baseline 3.

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 (search) and resource (Ravelry pattern database), then enumerates the filter dimensions. It is clearly distinct from sibling search_yarns, which covers a different resource.

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?

Tells the agent it returns a page of matches and explicitly routes follow-up work to get_pattern_details for yarn, gauge, needles and notes. It gives no when-not guidance or comparison to sibling searches, so it stops short of a 5.

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

Deploy Server