Skip to main content
Glama
Inferensys

Apollo.io MCP Server

by Inferensys

delete_note

Remove a note from Apollo by providing its ID to clean up your records.

Instructions

Delete a note from Apollo. FREE. Undocumented endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesNote ID to delete
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It mentions 'FREE' (cost implication) and 'Undocumented endpoint' (negative signal), but fails to disclose whether deletion is irreversible, authorization requirements, or side effects like cascading deletes.

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?

The description is very short, but includes extraneous phrases 'FREE.' and 'Undocumented endpoint.' that do not aid an AI agent. It could be more focused on essential details.

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?

For a simple deletion tool with no output schema and no annotations, the description is incomplete. It lacks information about response behavior, error handling, or constraints (e.g., cannot delete notes in use).

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% as the single parameter note_id has a clear description. The tool description adds no additional parameter information beyond what the schema already provides, so baseline score of 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 'Delete a note from Apollo,' which is a specific verb+resource. It distinguishes from sibling tools like create_note or delete_contact. However, the added 'FREE. Undocumented endpoint.' does not enhance purpose clarity.

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. The description does not specify prerequisites, such as whether the note must exist, or conditions under which deletion is allowed.

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