Skip to main content
Glama
Lead Gen Playbook MCP

Lead Gen Playbook MCP

List agents

list_agents
Read-onlyIdempotent

Retrieve lead-generation agents, optionally filtered by stage key, to select relevant sales prompts for a specific funnel stage.

Instructions

List the lead-generation agents, optionally filtered by stage key (see list_stages).

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_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoStage key, e.g. 'copywriting'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is fully covered by structured data. The description adds only that the filter is optional and where stage keys come from; it says nothing about ordering, result size, or what an agent record contains.

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?

A single sentence, front-loaded with the core action and scoped with the optional filter. The parenthetical cross-reference is short and directly useful; no filler.

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

Completeness3/5

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

For a one-parameter read-only list tool with rich annotations, the essential call information is present. The remaining gap is that with no output schema, the description never indicates what a returned agent looks like, which matters for deciding follow-up actions like get_agent.

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?

Schema coverage is 100% and the schema example ('copywriting') already anchors the stage parameter. The description goes beyond that by pointing to list_stages as the authoritative source of valid stage keys, which is genuine added meaning.

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?

The description gives a specific verb ('List') and resource ('lead-generation agents') with the optional filter named inline. It does not distinguish itself from the sibling search_agents, so an agent must still infer whether listing or searching is appropriate.

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?

It covers the filtered and unfiltered cases ('optionally filtered by stage key') and routes the agent to list_stages for valid keys. However, it gives no condition for choosing this over search_agents or get_agent, which is the main sibling ambiguity here.

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