MCP tool reference · #338 of 563 by publishers
get_playbook
Exposed by 10 servers from 10 publishers, read from the live servers by the Serverdex check; most of them sit in AI & Agents; 30% of them take a name parameter; the most-starred is Cloud FinOps Skill & MCP (75 stars).
get_playbook(name: string, …)Parameters
share = % of the 10 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| name | string | 30% | 66.7% | Playbook name, e.g. 'Attribution', 'CPQ', 'Sales Territory Design'. |
| field | — | 10% | 0% | — |
| framework_id | string | 10% | 100% | — |
| product | string | 10% | 0% | Only return guides for this product. |
| section | string | 10% | 0% | Optional section, e.g. 'Blueprint'. Omit for the whole playbook. |
| slug | string | 10% | 0% | — |
| stage | string | 10% | 0% | Chapter to return; omit for the index and the workflow. |
| title_keyword | string | 10% | 100% | — |
| vertical | string | 10% | 0% | Optional. A vertical slug. B2B SaaS: crm, martech, hrtech, fintech, cybersecurity, devtools. Consumer brands: ecommerce, consumerapps, hospitality, marketplaces |
Source: the input schema each server returns for get_playbook, aggregated over the 10 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with get_playbook
10 of 10 · 10 publishers · 10 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes get_playbook |
|---|---|---|---|---|---|---|
| 1 | Cloud FinOps Skill & MCPoptimnow · Cloud & DevOps | optimnow | Cloud & DevOps | 75 | yes | Fetch the step-by-step runbook for one specific waste pattern: symptoms, the detection queries to run, the fix, and the anti-pattern to avoid. Use this when the user asks how to detect, confirm, or fix one specific named waste pattern (zombie NAT gateway, snapshot sprawl, idle SageMaker endpoint, ...), including questions about the user's own resources ("which of my X...") |
| 2 | eightytwentyh3692 · Documents & Knowledge | h3692 | Documents & Knowledge | 5 | yes | The 80-20 slide-design methodology for case competition decks. Call it before planning a deck. With no stage it returns the index of stages and the workflow; pass a stage for one chapter. |
| 3 | MindThreadppcvote · Content & Publishing | ppcvote | Content & Publishing | 1 | yes | Returns the operating playbook for running an account through this server: the daily loop, how confirmation requests work, quotas, and the review checklist. The same text is in the initialize instructions. Applies when the instructions were not kept or the user asks how the service works. |
| 4 | Marketing Playbookssourabhjagga · AI & Agents | sourabhjagga | AI & Agents | — | yes | Retrieve full playbook text matching a specific title keyword within a framework. |
| 5 | Citehoundandacuzel · Databases | andacuzel | Databases | — | yes | Returns the full GEO/AEO playbook for one of Citehound’s fourteen verticals, as plain readable text: the strategic shift, three actionable strategies, outdated pitfalls to avoid, and an expert-tip placeholder. Called with no argument it returns the list of the fourteen verticals with their track (B2B SaaS, consumer and e-commerce brands, local and independent professionals), so call it with no arg |
| 6 | GammaRips Options Intelligencedevdizzle · AI & Agents | devdizzle | AI & Agents | — | yes | Methodology + reference, versioned server-side (re-fetch rather than caching long-term). Arg-driven: * `field` given — the plain-English DEFINITION + role of a signal field (deterministic lookup, no LLM). e.g. field="mom_60". The response's `available_fields` lists every documented field. * `name` given — a methodology playbook (markdown) by name, OR two sp |
| 7 | Runitonai MCPstructlabs-io · APIs & Integrations | structlabs-io | APIs & Integrations | — | yes | Stub — not implemented in Phase 1. See tool response 'phase' field. |
| 8 | Recaofernando-menendez · Developer Tools | fernando-menendez | Developer Tools | — | yes | Get a Recao GTM playbook: the go-to-market moves a solo app founder's agent runs, wired to the competitor data tools. Start with 'the-roadmap' (diagnoses the founder's stage and its binding constraint, then routes you to the right playbook). Call with no slug to list all playbooks. |
| 9 | LeanScale GTM Knowledgeleanscaleteam · Documents & Knowledge | leanscaleteam | Documents & Knowledge | — | yes | Retrieve a LeanScale delivery playbook in full, or one named section of it. Playbooks are structured Blueprint → Build → Enable → Maintain. Call list_playbooks first if you're not sure of the name. |
| 10 | gethal.aiai.gethal · Other | ai.gethal | Other | — | yes | Returns the HAL playbook: guides and cheat sheets on working with each product (for Outreach: what HAL does in each pipeline stage, and the requests customers send HAL most), with page URLs and PDF downloads in English and Danish. Optionally filter by product. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.