Skip to main content
Glama
Dweeb1578

Marketing Analytics MCP Server

by Dweeb1578

hubspot_search_deals

Search HubSpot deals using filters, properties, and sorting for read-only access to deal data.

Instructions

Search HubSpot deals with filters (READ-ONLY).

Args: filters: JSON string of HubSpot filter groups array. Example: '[{"filters":[{"propertyName":"dealstage","operator":"EQ","value":"closedwon"}]}]' properties: Comma-separated deal properties to return limit: Max deals to return (default: 20) sort_by: Property to sort by (default: "createdate") after: Cursor token from a previous call's next_cursor for pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
filtersNo[]
sort_byNocreatedate
propertiesNodealname,amount,dealstage,pipeline,createdate,closedate,primary_source

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It declares READ-ONLY and explains pagination, sorting, and filtering behavior, but does not mention rate limits or authentication.

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?

Concise and well-structured. Starts with a clear purpose sentence, then lists parameters with explanations. No redundant information.

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 tool's complexity and the presence of an output schema, the description covers filtering, sorting, pagination, and property selection. It is complete for a search tool.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each parameter, providing defaults, and giving an example for filters. This adds significant value beyond the schema.

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?

Clearly states it searches HubSpot deals with filters, and the title 'hubspot_search_deals' aligns. Among siblings like hubspot_search_companies, it distinguishes by resource.

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?

Provides detailed parameter explanations and an example for filters, but lacks explicit guidance on when to use this tool vs. alternatives like hubspot_get_deal or hubspot_search_contacts.

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/Dweeb1578/marketing-analytics-mcp'

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