Skip to main content
Glama
Sign In
Marketing Analytics MCP Server

Marketing Analytics MCP Server

by Dweeb1578
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

hubspot_pages_to_deals

Find contacts whose first or last analytics URL contains a specified pattern and retrieve their associated deals.

Instructions

Find contacts whose first/last analytics URL contains a pattern, plus their deals.

Args: url_pattern: URL substring (e.g. "/alternatives/chargebee") start_date: ISO date >= createdate (optional) end_date: ISO date <= createdate (optional) limit: Max contacts (default: 100)

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": {
      "url_pattern": "<url_pattern>"
    },
    "name": "hubspot_pages_to_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
end_dateNo
start_dateNo
url_patternYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations exist, so description must fully convey behavior. It mentions 'first/last analytics URL' but doesn't explain what that means or how matching works. Missing details on pagination, case sensitivity, or error conditions.

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?

Short and includes structured Args list. First sentence slightly redundant with name, but overall efficient. No wasted sentences.

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

Completeness3/5

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

Output schema exists, so return values are covered. Parameters are documented. However, behavioral details (pagination, error handling) are missing, leaving gaps for complex use cases.

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

Parameters4/5

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

With 0% schema coverage, description adds value by explaining each parameter: url_pattern as substring, start/end_date as ISO dates relative to createdate, limit with default. Example provided. However, 'first/last' semantics are unclear.

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?

Description clearly states it finds contacts based on URL pattern and retrieves their deals. This distinguishes it from sibling tools like hubspot_search_contacts or hubspot_get_contact_deals by adding the URL pattern matching specificity.

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?

No explicit guidance on when to use this vs. alternatives. The purpose implies usage for URL-based contact discovery, but no exclusions or comparisons are provided.

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