Skip to main content
Glama

Hubspot

by io.github.pipeworx-io

Hs List Companies

hs_list_companies
Read-onlyIdempotent

Browse all companies in your HubSpot workspace. Returns company IDs, names, domains, and properties. Paginate with limit and after parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor from a previous response
limitNoMaximum number of companies to return (default 10, max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagingNoPagination information
resultsNoArray of company objects

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "paging": {
+      "description": "Pagination information",
+      "properties": {
+        "next": {
+          "properties": {
+            "after": {
+              "description": "Cursor for next page",
+              "type": "string"
+            },
+            "link": {
+              "description": "Next page link",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "results": {
+      "description": "Array of company objects",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Company ID",
+            "type": "string"
+          },
+          "properties": {
+            "description": "Company properties (name, domain, industry, etc.)",
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 30
+  },
+  {
+    "after": "next_page_cursor_xyz789",
+    "limit": 50
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by specifying returned fields and pagination behavior, which are beyond the annotations.

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 with no waste: first states purpose, second states output and pagination. Efficient and front-loaded.

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

Completeness5/5

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

Given the simple list tool with annotations and output schema present, the description covers the necessary context: what it returns and how to paginate. No gaps remain.

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 100% with clear descriptions for both parameters. The description only mentions pagination generally without adding new meaning, so it meets the baseline for high coverage.

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 uses 'Browse all companies in your HubSpot workspace' to clearly indicate a list operation. It distinguishes from sibling tools like hs_get_company (single) and hs_list_contacts (different entity) by specifying the resource and scope.

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?

While it implies use for listing companies, it does not provide explicit guidance on when to use this tool vs alternatives like search or single retrieval. No when-not or alternative tools are mentioned.

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

All Hubspot toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools are near-duplicates or overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve overlapping query/discovery purposes. The polymarket tools and HubSpot tools are more distinct, but the set as a whole has fuzzy boundaries between many members.

Naming Consistency2/5

Naming is inconsistent across the set: HubSpot tools use an hs_ prefix, Pipeworx tools mostly use bare verbs (ask_pipeworx, recall, forget), and other tools mix styles (ai_visibility_check, generate_llms_txt, polymarket_edges). The hs_* subset is consistent, but overall there is no single predictable pattern.

Tool Count2/5

38 tools is too many for the apparent scope, especially since the server is named 'Hubspot' but only 6 of the tools are HubSpot-specific. A large portion of the catalog covers unrelated Pipeworx data access, prediction markets, memory, and npm scanning, making the set feel bloated and unfocused.

Completeness2/5

The HubSpot portion of the tool set is read-only: it can get, list, and search companies/contacts/deals, but has no create, update, or delete operations, leaving obvious lifecycle gaps. If the intended domain is actually Pipeworx/data research, the HubSpot tools seem like an unrelated afterthought, so the surface is incomplete for either interpretation.

Resources