Skip to main content
Glama

List GTM Vault playbooks

list_playbooks
Read-only

List the GTM Vault playbooks: multi-step workflows such as gtm-audit, build-my-stack, tool-check and decision-memo, plus the Skills group: operator skills built from systems on the record (PQL scoring, review signals, account monitoring, win-loss, Claude Code outbound, cold email, MCP enrichment, agents behind the rep, revenue intelligence, AI search citation, BDR intent action layer, browser enrichment actions, headless AE dashboard, LinkedIn outbound with Loom demos, niche down to expand, GTM engineer rollout on Clay, revenue context layer, self-learning support loop) and the operating skills GTM Vault itself runs on (episode write-ups, trailer briefs, thumbnails, the signals and AI citation rails). Call when the user asks what GTM Vault can do or which playbook or skill fits their problem.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_playbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results include both playbooks and a Skills group, which is useful content context, but says nothing about ordering, format, or size of the returned list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the bulk of the text is a roughly 20-item parenthetical enumeration of individual skill names (PQL scoring, review signals, cold email, MCP enrichment, thumbnails, and so on). An agent gains nothing from that list before calling a zero-argument listing tool that will return it anyway, so much of the description does not earn its place.

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?

For a parameterless read-only listing tool with no output schema, the description covers the essentials: what it returns at a high level and when to call it. The over-enumeration is a style problem rather than a completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the GTM Vault playbooks') and clarifies what a playbook is ('multi-step workflows'). It implicitly contrasts with the sibling get_playbook by being a listing operation, but never explicitly names that alternative.

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?

Gives a clear trigger: 'Call when the user asks what GTM Vault can do or which playbook or skill fits their problem.' It does not state when-not to use it or name search_vault/get_playbook as the alternative for narrower lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources