Conecto

Change a HubSpot record

hubspot_update

Change properties of a contact, company, deal or ticket in the company's HubSpot. On accounts with an owner it waits for the owner's approval by default, showing each property's value now and after. $0.001. Costs $0.001 per call; nothing if it fails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object": "<object>",
      "id": "<id>",
      "properties": "<properties>"
    },
    "name": "hubspot_update"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The record's HubSpot id.
`object`	Yes	contacts, companies, deals or tickets.
`properties`	Yes	HubSpot property names and values, like {"dealstage": "closedwon", "amount": 18400}.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds genuinely new behavior: writes may be gated on owner approval by default and the approval shows before/after values per property, plus a per-call cost with no charge on failure. That is meaningful disclosure beyond the structured hints, though it never states that repeated calls may produce different results (idempotentHint=false) or what the success response looks like.

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

Conciseness4/5

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

Front-loaded with the action and target, then the approval behavior. Slightly wasteful in restating the price twice ('$0.001. Costs $0.001 per call'), which costs it a point.

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 mutation tool with no output schema and rich annotations, the description covers the risky unknowns an agent cares about: approval gating, cost, and no charge on failure. It omits what happens to properties not included in the call and what a successful response contains, minor gaps for an update operation.

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 description coverage is 100% – all three parameters are documented with the enum, the ID pattern, and an example property map. The description adds nothing parameter-specific beyond restating the object types already enumerated in the schema, so baseline 3 applies.

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?

States a specific verb ('Change properties of') and enumerates the four supported record types, so the agent knows exactly what it mutates. It is distinguishable in spirit from hubspot_create and hubspot_get, though it never names those siblings explicitly.

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?

Usage is only implied by the name and verb – there is no statement of when to choose this over hubspot_create, crm_update_contact, or salesforce_update. The owner-approval note gives context about what will happen, not about which situations call for this tool.

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

All Conecto tools Inspect

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

Need Help?