Tailwind App

list_group_boards

Read-onlyIdempotent

Use this when the user wants to see what public Pinterest group boards exist for a topic, or wants benchmark context for how boards in their niche are named and sized. Returns public collaborative boards matching a keyword from Tailwind's Group Board Finder. These are OTHER people's public boards — they are not the user's own boards (use list_boards for those), and their board ids cannot be passed to create_post or schedule_post. Results are cached and refreshed in the background, so check status before reporting: ready means the boards returned are what we have (an empty list means a completed search genuinely found none), warming means a search is still running and you should tell the user to check back rather than reporting no results, and unavailable means the search failed and no benchmark data can be given for this keyword. Tailwind Communities (formerly Tribes) has no tool here: these tools cannot list the user's Communities, share Pins to one, or read how a Community performs. Tailwind is replacing Communities with Turbo Groups, niche groups of creators who see and engage with each other's Pins in Turbo, which the user joins from suggestions in their Turbo feed and finds again under My Groups in the Tailwind app. Turbo Groups has no tool either. A request for either one is a missing capability that request_capability records; Pinterest group boards (list_group_boards) are a different feature and do not answer it.

Input Schema

Name	Required	Description	Default
`keyword`	Yes	Topic to search for, e.g. "home decor". Trimmed, whitespace-collapsed and lowercased before lookup; 100 characters maximum. Use the user's actual niche terms rather than a broad category.

Output Schema

Name	Required	Description
`boards`	Yes	Public group boards matching the keyword, most-followed first
`status`	Yes	`ready` — the boards are what we have, including an empty list. `warming` — a search is running and nothing is cached yet. `unavailable` — the most recent search failed.
`keyword`	Yes	The normalized keyword the results are keyed on
`lastCompletedAt`	No	When a search for this keyword last completed successfully
`retryAfterSeconds`	No	On `warming`, how long to wait before asking again

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/open-world, but the description adds behavior the annotations cannot: caching with background refresh and the three-state `status` contract, including that `warming` must not be reported as 'no results'. It also warns that returned board ids are unusable downstream, which prevents a concrete misuse.

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?

Front-loaded with the trigger, the sibling contrast, and the status contract in that order. The Communities/Turbo Groups paragraph is long relative to the tool's core job, but it earns its place by preventing misfires on unsupported requests.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing (so return shape needn't be spelled out), the description still supplies the status semantics needed to interpret that output correctly. Safety, scope, alternatives, and failure modes are all covered.

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 only parameter's description already covers normalization, length limit, and niche-term guidance. The description adds only the 'matching a keyword from Tailwind's Group Board Finder' framing, so the schema does the heavy lifting — 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 and resource (list public Pinterest group boards), names the data source (Tailwind's Group Board Finder), and explicitly contrasts with list_boards. An agent can distinguish this from every sibling without opening the schema.

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?

Gives explicit trigger conditions (user wants to see public boards for a topic or benchmark naming/sizing), an explicit exclusion with the correct alternative (use list_boards for the user's own boards), and rules out create_post/schedule_post consumers. It also pre-empts two related-but-unsupported requests (Communities, Turbo Groups) and points to request_capability.

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

All Tailwind App tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?