Skip to main content
Glama
adeel0x01

HubSpot MCP Server

by adeel0x01

hubspot_search_email_engagements

Search email engagements in HubSpot using queries and property filters to retrieve specific interactions.

Instructions

Search email engagements in HubSpot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
queryNo
filtersNoFilter criteria
propertiesNo
Behavior2/5

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

No annotations provided, and the description fails to disclose whether this tool is read-only, destructive, or requires specific permissions. It only restates the tool's name in sentence form.

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?

While concise, the description is too short to be useful. It lacks structure and front-loads no actionable information beyond 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?

Given no output schema, numerous sibling tools, and 5 parameters, the description is critically incomplete. It fails to cover return value format, pagination behavior, or how filters work.

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

Parameters1/5

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

With only 20% schema coverage, the description adds no parameter details. Parameters like 'after', 'limit', 'query', and 'properties' remain unexplained, forcing the agent to guess their meanings.

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?

The description states the tool searches email engagements, but it is too vague and does not specify what constitutes an email engagement or differentiate from other search tools among siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 others like hubspot_search_calls or hubspot_list_email_engagements. No context on appropriate scenarios or limitations.

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/adeel0x01/hubspot-mcp-tools'

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