Skip to main content
Glama
Inferensys

Apollo.io MCP Server

by Inferensys

create_opportunity

Add a deal to Apollo CRM by providing a name and optionally setting amount, stage, close date, owner, account, or contacts.

Instructions

Create a new deal/opportunity in your Apollo CRM. FREE. At minimum, provide a name. Optionally set amount, stage, close date. Undocumented endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDeal/opportunity name
amountNoDeal value in dollars
opportunity_stage_idNoStage ID (use list_opportunity_stages to get IDs)
owner_idNoOwner user ID
closed_dateNoExpected close date, e.g. '2026-03-15'
account_idNoAssociated account/company ID
contact_idsNoAssociated contact IDs
Behavior2/5

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

No annotations provided. Description only says 'FREE' and 'Undocumented endpoint' but does not disclose behavioral traits like side effects, required permissions, or safety. As a creation tool, mutation is implied but not detailed.

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

Conciseness3/5

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

Short but disjointed with abrupt period between 'FREE' and 'At minimum'. Includes unnecessary 'Undocumented endpoint' phrase. Could be more polished.

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?

Lacks output information, error handling, prerequisites, and detailed behavior. Leaves gaps for a tool with 7 parameters and no annotations.

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 coverage is 100%, so baseline is 3. Description adds minimal extra meaning by summarizing optional fields, but mostly restates schema info.

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?

Clearly states 'Create a new deal/opportunity' with specific verb and resource. Siblings are other create tools for different entities, so no confusion.

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 explicit when-to-use or alternatives. Only gives minimal parameter input guidance ('At minimum, provide a name'). Does not distinguish from other create tools.

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/Inferensys/apollo-io-mcp'

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