AIsa Sales

Get a List of Notes

get_apollo_notes

Read-onlyIdempotent

Notes attached to workspace records. ⚠️ At least one filter is required — calling it bare returns HTTP 400 with "At least one argument is required". Pass one of contact_id, account_id, opportunity_id, calendar_event_id, conversation_id, conversation_ids, contact_ids or a start_date. The spec marks every one of them optional individually, which is true only in the sense that no single one is mandatory.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (when supported). At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`per_page`	No	Results per page (when supported). At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`account_id`	No	Filter by an account ID. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`contact_id`	No	Filter by a contact ID. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`start_date`	No	Only include notes created on/after this date (when supported). At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`contact_ids`	No	Filter by contact IDs. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`opportunity_id`	No	Filter by an opportunity ID. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`conversation_id`	No	Filter by a conversation ID. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`conversation_ids`	No	Filter by conversation IDs. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".
`calendar_event_id`	No	Filter by a calendar event ID. At least one filter is required on this endpoint; calling it with none returns HTTP 400 "At least one argument is required".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description discloses the HTTP 400 error behavior and explicitly warns that the schema's 'optional' flags are misleading—valuable context beyond the annotations (readOnlyHint, idempotentHint, etc.). It adds meaningful behavioral information without contradicting the annotations.

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 compact—two sentences—with the core purpose first and the critical warning second. It avoids redundancy with the schema and earns its length.

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?

For a 10-parameter read tool with a full input schema and an output schema (indicated), the description covers the most important behavioral gotcha (mandatory filter) and is sufficient for an agent to invoke it correctly. It does not mention pagination or return format, but those are handled by the schema and output schema, so nothing essential is missing.

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%, so each parameter already has a descriptive comment. The tool description lists the filter options but adds no new meaning beyond the schema—it merely repeats the filter names. The filter-requirement warning is already embedded in every schema parameter description, so the description provides no incremental parameter insight.

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 states a clear verb and resource ('Notes attached to workspace records'), which immediately conveys what the tool returns. It lists the specific filter parameters, adding precision. Although it does not explicitly contrast with siblings, none of the many sibling tools appear to overlap with note retrieval, so the purpose is unambiguous.

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 gives crucial usage guidance: at least one filter is required, otherwise the endpoint returns HTTP 400. It also clarifies that the spec's per-parameter 'optional' markings are misleading. However, it does not mention when to choose this tool over alternatives or any exclusions, so it falls short of full guidance.

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

All AIsa Sales tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?