The Revenue AI Report

List playbooks

list_playbooks

Read-onlyIdempotent

Browse the GTM AI playbook library from The Revenue AI Report. Each playbook is a sequenced workflow with owner, tool, pitfalls, definition of done, and KPIs, mapped to a team and to an L1 to L6 AI maturity level. Filter by team, maturity level, or keyword.

Input Schema

TableJSON Schema

Name	Required	Description
`team`	No	Team or category. One of: cs, enablement, general, marketing, org, revops, sales.
`limit`	No	Default 30.
`query`	No	Keyword filter on title, summary, and tags.
`maturity`	No	AI maturity level, L1 to L6.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`teams`	Yes
`total`	Yes
`matched`	Yes
`returned`	Yes
`playbooks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "matched": {
+      "type": "number"
+    },
+    "playbooks": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "maturity": {
+            "type": "number"
+          },
+          "maturityLabel": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "steps": {
+            "type": "number"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "team": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "summary",
+          "team",
+          "maturity",
+          "maturityLabel",
+          "steps",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "type": "number"
+    },
+    "teams": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "matched",
+    "returned",
+    "teams",
+    "playbooks"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds useful content context about playbook structure and maturity levels, but does not disclose additional behavioral traits such as auth requirements, rate limits, or pagination behavior beyond what schema already covers.

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?

The description is three sentences with no filler: purpose, playbook content model, and filter options. It is front-loaded and every sentence earns its place, making it easy for an agent to scan and understand quickly.

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?

Given the output schema exists and all four optional parameters are fully documented, the description is largely complete for a read-only list operation. It names the relevant filters and the data domain; only an explicit pointer to get_playbook for single-item retrieval is missing.

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%, with team, limit, query, and maturity all individually documented. The description's mention of filtering by team, maturity level, or keyword mirrors the schema without adding new syntax or format details, so the baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Browse the GTM AI playbook library.' It further distinguishes itself from sibling list tools by describing the unique playbook structure and naming the three filter dimensions, so an agent can clearly tell it apart from list_prompts, list_resources, and similar tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies the tool is for browsing and filtering playbooks by team, maturity, or keyword, but it does not explicitly explain when to choose this over the sibling get_playbook or other list_* tools. Usage context is present, but exclusions and alternative routing are left to inference.

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

All The Revenue AI Report 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?