Skip to main content
Glama
Lead Gen Playbook MCP

Lead Gen Playbook MCP

Search agents

search_agents
Read-onlyIdempotent

Find sales-agent prompts by keyword across names, goals, inputs, and outputs to locate matching lead-generation workflows and copy-ready prompts.

Instructions

Keyword search across agent names, goals, inputs and outputs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesKeywords, e.g. 'follow up email'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful detail that matching spans names, goals, inputs, and outputs, but says nothing about match semantics (substring vs token), ranking, or empty-result behavior.

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 front-loaded sentence with zero filler; the covered fields are listed immediately after the core action. Nothing is wasted and nothing needs reordering.

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 simple two-parameter read-only search with full schema coverage and strong annotations, this is close to sufficient. What is missing is the routing information an agent needs to pick this over list_agents or recommend_agents, which matters given seven search-adjacent siblings.

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 'query' documented as keywords and 'limit' capped at 25 with a default of 10. The description's only addition is clarifying which fields the query is matched against, which is mildly useful but does not explain syntax, multi-word handling, or limit behavior — baseline 3.

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 (keyword search) and resource (agents) and enumerates the searched fields: names, goals, inputs, and outputs. It is clearly distinguishable from get_agent or list_agents, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

It states what search does but gives no when-to-use guidance: nothing says when to use this versus list_agents, get_agent, or recommend_agents, nor whether it suits discovery versus exact lookup. The usage context is only implied by the words 'keyword search'.

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