Skip to main content
Glama
MSPbotsAI

keap-mcp

by MSPbotsAI

keap_create_opportunity

Create a sales opportunity (deal) for a contact, assign it to a pipeline stage, and set title, estimated close date, and revenue.

Instructions

Create a sales opportunity (deal).

    API: POST /opportunities

    Args:
        contact_id: Required. The contact ID this opportunity is for.
        stage_id: Required. The pipeline stage ID to place it in.
        opportunity_title: Required. Title of the opportunity.
        user_id: The owning user's ID.
        next_action_date: ISO 8601 date/time for the next action.
        next_action_notes: Notes for the next action.
        opportunity_notes: General notes on the opportunity.
        estimated_close_date: ISO 8601 date for the estimated close.
        projected_revenue_low: Low end of the projected revenue range.
        projected_revenue_high: High end of the projected revenue range.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNo
stage_idYes
contact_idYes
next_action_dateNo
next_action_notesNo
opportunity_notesNo
opportunity_titleYes
estimated_close_dateNo
projected_revenue_lowNo
projected_revenue_highNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states it creates an opportunity and lists parameters; it doesn't mention permissions, idempotency, response behavior, or side effects. The API line adds minimal context beyond what the name implies.

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 efficiently organized: a one-line purpose, the API path, then a bullet-like list of parameters. No wasted words, though the API line is marginally redundant with the tool name. Front-loaded with the core intent.

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?

The tool is a create operation with 10 parameters and an output schema, so parameter coverage is high. However, it lacks any usage guidance, behavioral context (e.g., whether revenue ranges are inclusive, how dates are interpreted), or caveats. Acceptable but with clear gaps for a tool of this complexity.

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?

The schema has zero description coverage for its 10 parameters, but the tool description compensates by providing one-line explanations for each parameter, including which are required (though the schema already marks those). This gives the agent meaningful semantics beyond raw type names.

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 opens with 'Create a sales opportunity (deal)' – a specific verb and resource. It also names the underlying API endpoint, making the action unambiguous and distinct from sibling tools like keap_get_opportunity or keap_list_opportunities.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or typical scenarios. It only lists parameters, leaving the agent to infer usage from the tool name and sibling context.

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