Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Connect HubSpot

hubspot_connect

Connect the company's own HubSpot, which stays the source of truth: the agent finds, reads and changes contacts, companies, deals and tickets there. The company makes a service key in HubSpot (Settings, Integrations, Service Keys) with the CRM scopes the agent may use, or uses a private app's token. Called without token, it answers with a link for the owner, who types it on a Conecto page, so it never passes through the chat (from_a_terminal does the same from a terminal); account.credential_added says when it is connected. The token is checked before anything is kept. On accounts with an owner, changing an existing record waits for the owner's approval by default. Free. Free.

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

Input Schema

NameRequiredDescriptionDefault
tokenNoThe service key or private app token. Never shown again. Leave it out to get the link instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / token / description
      Previous value: -"The private app's access token. Never shown again."New value: +"The service key or private app token. Never shown again. Leave it out to get the link instead."
    • changedInput schema / required
      Previous value: -[
-  "token"
-]New value: +[]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as non-read-only, open-world, non-idempotent and non-destructive, and the description adds real context beyond that: the token is validated before anything is kept, secrets never pass through chat, owner approval gates record changes, and the account.credential_added event signals success. It does not describe what happens on an invalid or revoked token, which is the main remaining gap.

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

Conciseness3/5

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

The content is mostly substantive, but the delivery is a dense run-on with parenthetical tangents and a duplicated 'Free. Free.' at the end. It would land harder if the auth steps, the link flow, and the approval rule were separated into short front-loaded sentences.

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?

For a one-parameter connection tool with no output schema, the description covers setup, the secret-handling model, the alternative link flow, the approval default, and the completion signal. Failure modes and the disconnect path are the only notable omissions.

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?

There is a single parameter at 100% schema description coverage, so the schema already documents that the token is write-only and that omitting it yields a link. The description restates this rather than adding new syntax or format detail, so the baseline 3 applies.

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 first sentence names a specific verb and resource ('Connect the company's own HubSpot') and immediately scopes what the agent can then do (find, read, change contacts, companies, deals, tickets), which distinguishes it from siblings like hubspot_search or hubspot_get. An agent can identify the tool without opening the schema.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the two invocation paths clearly: with a token, or without one to receive a link the owner types on a Conecto page, and notes from_a_terminal as the terminal equivalent. It also states the default approval rule for changing existing records. What it doesn't do is explicitly route to hubspot_disconnect or compare against other connection tools such as salesforce_connect.

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

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources