Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

hubspot.v2.get_timeline_events

Retrieve timeline events for HubSpot objects (companies, contacts, deals, tickets) with filters by date range, event type, and properties.

Instructions

Get HubSpot Timeline Events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
source_object_idYesID of the object to retrieve timeline events for.{{company_id}}
event_type_filterNoOptional filter by specific event type.deployment_completed
propertiesNoSelect properties to retrieve from timeline events
start_dateNoOptional date range to filter timeline events (mm/dd/yyyy format).
end_dateNoOptional date range to filter timeline events (mm/dd/yyyy format).
result_limitNoMaximum number of timeline events to return (default: 100, max: 500).100
output_variable_nameYesVariable name to store the timeline events.timeline_events
Behavior1/5

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

No annotations exist, and the description provides no behavioral details like pagination, rate limits, or required permissions, leaving the agent uninformed.

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?

Description is overly brief, lacking essential details; conciseness is not effective when it omits needed information.

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 fails to provide sufficient context for correct invocation.

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 baseline is 3; description adds no additional meaning beyond what schema already provides.

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

Purpose2/5

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

Description 'Get HubSpot Timeline Events' is generic and only restates the function of the tool without distinguishing it from sibling tools like 'get_engagements' or 'get_hubspot_object'.

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 provided on when to use this tool versus alternatives, such as other HubSpot data retrieval 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/OnStartups/agentai-mcp-server'

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