Skip to main content
Glama
MSPbotsAI

keap-mcp

by MSPbotsAI

keap_list_campaigns

Find and list Keap marketing and automation campaigns by searching by name, controlling page size, and sorting results for targeted retrieval.

Instructions

List marketing/automation campaigns.

    API: GET /campaigns

    Args:
        search_text: Free-text search on campaign name.
        limit: Max results per page.
        offset: Pagination offset.
        order: Sort field, e.g. "id", "name", "published_date", "status", "category".
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
orderNo
offsetNo
search_textNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the HTTP method (GET), which signals a read-only operation, and gives parameter meanings. It does not mention pagination behavior or response shape, but the output schema likely covers the latter.

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 compact and well-organized with a clear purpose statement, API endpoint, and parameter list. There is no redundant text; every line adds value.

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 tool's simplicity, the description covers the essential aspects: purpose, endpoint, and parameter semantics. The presence of an output schema handles return value documentation, making this description sufficient.

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

Parameters5/5

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

The input schema has no property descriptions (0% coverage). The description adds concise explanations for all four parameters, including examples for the 'order' field, fully compensating for the schema's lack of detail.

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 clearly states 'List marketing/automation campaigns' which is a specific verb+resource. This distinguishes the tool from sibling tools that list contacts, opportunities, notes, tasks, and users.

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 provides only the basic purpose and parameter list; it does not explicitly state when to use this tool over alternatives. Since there is no other campaign-related tool among siblings, usage is implied but not explicitly contrasted.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MSPbotsAI/keap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server