Skip to main content
Glama
BusyBee3333

Keap MCP Server

by BusyBee3333

keap_list_contacts

List your Keap contacts with pagination, filter by email, name, or date range, and sort results.

Instructions

List contacts with pagination, filtering, and sorting options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoFilter by email address
limitNoNumber of results per page (max 200)
orderNoField to order by (e.g., date_created, email)date_created
sinceNoFilter contacts created/updated after this ISO date
untilNoFilter contacts created/updated before this ISO date
offsetNoOffset for pagination
given_nameNoFilter by first name
family_nameNoFilter by last name
order_directionNoSort direction
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits such as rate limits, authentication requirements, or pagination behavior. It only mentions options without any behavioral context.

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

Conciseness4/5

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

The description is a single sentence that is front-loaded and concise. It covers the essence without waste, though it could benefit from slightly more detail.

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

Completeness2/5

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

The description does not explain what the tool returns (e.g., a list of contact objects with specific fields). Since there is no output schema, the description should provide this context.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond grouping them as 'filtering and sorting options.' Baseline 3 is appropriate.

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 clearly states it lists contacts with pagination, filtering, and sorting options. However, it does not differentiate from the sibling tool keap_search_contacts, which might have similar functionality.

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?

No guidance on when to use this tool versus alternatives like keap_search_contacts or keap_get_contact. The description does not mention any specific use cases or exclusions.

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/BusyBee3333/keap-mcp-2026-complete'

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