Skip to main content
Glama
MSPbotsAI

keap-mcp

by MSPbotsAI

keap_list_opportunities

List sales opportunities (deals) from Keap CRM. Filter by owner, stage, or search term, and control pagination and sorting to review pipeline.

Instructions

List sales opportunities (deals).

    API: GET /opportunities

    Args:
        user_id: Filter by the owning user's ID.
        stage_id: Filter by pipeline stage ID.
        search_term: Free-text search.
        limit: Max results per page.
        offset: Pagination offset.
        order: Sort field, e.g. "next_action", "opportunity_name", "contact_name", "date_created".
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
orderNo
offsetNo
user_idNo
stage_idNo
search_termNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations are absent, so the description bears the full burden. It discloses the API method (GET), filter semantics, and sort options, which is useful. However, it does not explicitly state that this is a read-only operation, mention authentication requirements, or describe edge cases like pagination behavior beyond offset/limit. The read-only nature is implied by 'List' but not explicitly confirmed.

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-structured: a one-sentence purpose, the endpoint, and a bullet-style Args list. It is front-loaded with the core function and every line adds value without redundancy.

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 complexity (6 optional parameters) and existence of an output schema, the description covers the essential aspects: purpose, endpoint, and all parameter meanings. It lacks minor details such as default sorting direction or search behavior, but is generally complete for invoking the tool.

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?

Schema description coverage is 0%, but the description provides meaningful explanations for all six parameters, including filter semantics and sort field examples. This fully compensates for the missing schema descriptions, giving the agent clear guidance on how to construct calls.

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 sales opportunities (deals)' using the specific verb 'list' and resource 'opportunities', distinguishing it from sibling tools like get_opportunity and create_opportunity. It also specifies the API endpoint, which reinforces its purpose.

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 implies the tool is used for listing opportunities and provides filter parameters, but it does not explicitly state when to use this tool over alternatives such as get_opportunity or create_opportunity. There is no exclusionary guidance or comparison with siblings.

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