Skip to main content
Glama
Sign In
mcpship-hubspot

mcpship-hubspot

by onemore-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_deals

Find HubSpot deals by name; omit the query to list recently modified deals and see what you touched this week.

Instructions

Search HubSpot deals by name. With no query, returns the most recently modified deals — use this for questions like 'what deals did I touch this week'.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return (HubSpot caps a page at 100).
queryNoDeal name fragment. Omit to list recent deals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It usefully discloses the default sort/scope when query is omitted, but says nothing about read-only semantics, required scopes/permissions, pagination behavior, or which deal fields come back.

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 short sentences with zero waste; the core action and the default behavior are front-loaded, and the example illustrates usage rather than padding.

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 simple two-parameter, zero-required read tool with no output schema, the description covers what the tool does and what happens with an empty query. Missing only secondary details such as sort order guarantees and returned field set.

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%, so both parameters are already documented, and the description largely restates them while adding that the query matches name fragments and that omission switches to recent listing. That is a modest semantic addition over the schema, consistent with the baseline 3.

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 names a specific verb and resource ("Search HubSpot deals by name") and states the default listing behavior, so an agent can tell it apart from search_contacts and the note tools by resource alone. It stops short of explicitly contrasting with siblings, but the resource boundary is unambiguous.

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 clearly states the no-query case (recently modified deals) and grounds it in a concrete example question, which is genuine when-to-use guidance. It gives no when-not-to-use guidance or pointer to alternative tools for broader filtering, so it falls short of a 5.

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

Deploy Server

Other Tools