Skip to main content
Glama
nubiia-dev

@iamsamuelfraga/mcp-hubspot

by nubiia-dev

hubspot_crm_list

Fetch paginated lists of HubSpot CRM objects (deals, line items, products, quotes, engagements). Use the properties parameter to select custom fields.

Instructions

List HubSpot CRM records of any object type (deals, line_items, products, quotes, calls, meetings, tasks, notes, emails). Returns a paginated collection with shape { results, total, pagination: { nextCursor } | null }. IMPORTANT: HubSpot returns only default properties unless you specify them explicitly via the properties parameter (e.g., "dealname,amount,closedate"). Use pagination.nextCursor from the response as the after parameter to page through large result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor from `pagination.nextCursor` in the previous response.
limitNoRecords per page (1–100). Default: 10.
archivedNoWhen true, returns archived (soft-deleted) records instead of active ones. Default: false.
objectTypeYesCRM object type. Sales objects: deals, line_items, products, quotes. Engagement objects: calls, meetings, tasks, notes, emails.
propertiesNoComma-separated list of property internal names to include in the response (e.g., "dealname,amount,closedate"). HubSpot returns ONLY default properties unless requested explicitly — always specify the properties you need.
associationsNoComma-separated list of object types to include as associations (e.g., "contacts,companies"). Returns associated record IDs inline.
Behavior3/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 discloses the paginated response shape and the behavior that only default properties are returned unless specified. It does not mention rate limits, authentication needs, or any side effects, but for a read-only list operation, the disclosed info is adequate.

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?

The description is concise: two sentences and an important note. Everything is front-loaded with purpose and key behavior. Every sentence adds value without redundancy.

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?

Given no output schema, the description explains the return shape and pagination mechanism. It covers all key aspects: supported object types, properties default, archived flag. It does not mention error responses or edge cases, but for a list tool, this is sufficient. The complexity (6 params, 1 required) is well-addressed.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds significant value by explaining how to use the `properties` parameter (e.g., 'dealname,amount,closedate') and how pagination works with `pagination.nextCursor`. This context helps the agent correctly construct requests beyond what the schema provides.

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 clearly states the tool lists HubSpot CRM records for multiple object types, with specific verb 'list' and resource 'CRM records'. It lists all supported object types and mentions pagination shape. However, it does not explicitly differentiate from sibling tools like hubspot_crm_search, which might be used for filtered listing.

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 includes important usage notes about default properties and pagination, which guide correct invocation. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., search for filtering, get for single record) and does not state when not to use it.

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/nubiia-dev/mcp-hubspot'

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