Skip to main content
Glama
Sign In
Apollo.io MCP Server

Apollo.io MCP Server

by Inferensys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_notes

Search notes in Apollo workspace by keyword or contact. Retrieve notes attached to contacts, accounts, or opportunities.

Instructions

Search notes in your Apollo workspace. FREE. Notes can be attached to contacts, accounts, or opportunities. Undocumented endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
q_keywordsNoKeyword search in notes
contact_idNoFilter notes for a specific contact
pageNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations provided, so description carries full burden. It only states 'Undocumented endpoint' and provides no behavioral traits such as whether it is read-only, destructive, or rate-limited. This is a significant gap for a search tool.

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 short but includes unnecessary text: 'FREE' and 'Undocumented endpoint' add no value. The first sentence is clear, but the fluff reduces conciseness.

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?

With 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return format, pagination behavior, or how filtering across attached entities works.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (q_keywords and contact_id have descriptions). The description does not add meaning beyond the schema; it repeats 'Search notes' without clarifying parameter usage, defaults, or pagination for page/per_page.

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?

Description clearly states 'Search notes in your Apollo workspace', identifying the verb and resource. It also mentions notes can be attached to contacts, accounts, or opportunities. However, it does not differentiate from sibling search tools like search_contacts or search_accounts.

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 lacks prerequisites, context, or exclusions. The only hint is that notes are attached to other entities, but no explicit usage scenario.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools