Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

hubspot.v2.get_engagements

Fetch notes, calls, emails, meetings, and tasks associated with a HubSpot object, with optional date and property filters.

Instructions

Get HubSpot Engagements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
source_object_idYesID of the object to retrieve engagements for.{{contact_id}}
engagement_typesNoSelect which types of engagements to retrieve.
propertiesNoSelect properties to retrieve from engagements
start_dateNoOptional date range to filter engagements (mm/dd/yyyy format).
end_dateNoOptional date range to filter engagements (mm/dd/yyyy format).
output_variable_nameYesVariable name to store the engagement history.engagement_history
result_limitNoMaximum number of engagements to return (default: 100, max: 500).100
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'Get', implying read-only, but fails to disclose pagination, rate limits, or behavior with large result sets. The schema includes result_limit but the description ignores it.

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

Conciseness2/5

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

The description is a single sentence, but it is under-specified and lacks structure. It does not front-load key information or earn its place; it essentially repeats the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what engagements are, how filtering works, or what the return format is, making it inadequate for an agent to use correctly.

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 88%, so the schema already documents most parameters. The description adds no additional meaning beyond what is in the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get HubSpot Engagements' which is a clear verb and resource, but it does not differentiate from sibling tools like hubspot.v2.create_engagement or hubspot.v2.get_timeline_events. It is minimally adequate but lacks distinguishing details.

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?

There is no guidance on when to use this tool versus alternatives such as search_objects or create_engagement. The description does not mention context or prerequisites for use.

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/OnStartups/agentai-mcp-server'

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