hubspot-mcp

hs_list_owners

List HubSpot users eligible to own CRM records, optionally filtering by email to find a specific rep.

Instructions

List HubSpot users (owners) that can be assigned to CRM records. Filter by email to look up a specific rep.

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": "hs_list_owners"
  }
}

Input Schema

Name	Required	Description	Default
`email`	No	Filter by owner email address
`includeInactive`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided, so description carries behavioral transparency. It indicates listing and filtering but does not disclose effects of includeInactive parameter, auth needs, or rate limits. Partial but not comprehensive.

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

Conciseness5/5

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

Two sentences, front-loaded with core purpose. No fluff, efficient and clear.

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

Completeness3/5

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

Given two parameters and no output schema, the description covers the purpose and one use case but omits explanation of includeInactive, return format, or pagination. Adequate but not fully complete.

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 coverage is 50% with email parameter having a schema description and includeInactive lacking one. The description adds no value beyond the schema for email and completely ignores includeInactive. Thus it does not compensate for the missing schema description.

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

Purpose5/5

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

The description clearly states the tool lists HubSpot users (owners) assignable to CRM records and mentions filtering by email. It distinguishes itself from sibling list tools like hs_list_forms.

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 implies usage for looking up a specific rep via email, but lacks explicit when-not-to-use or alternatives. No comparison with other tools, though no direct sibling duplicates its function.

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