Skip to main content
Glama

Crm Connector

crm_connector
Read-onlyIdempotent

Customer relationship management across HubSpot and LeadConnector: contacts, deals, pipelines, companies, and sales opportunities. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

NameRequiredDescriptionDefault
actionYeslist_hubspot_contacts: List HubSpot contacts using legacy API pagination | search_hubspot_contacts: Search HubSpot contacts by keyword | list_hubspot_deals: List HubSpot deals with pagination | list_leadconnector_contacts: List LeadConnector contacts with optional filters. Requires LeadConnector authentication | get_hubspot_account_info: Get HubSpot account and portal metadata for the authenticated user | get_hubspot_contact: Get full details for a HubSpot contact by ID | list_hubspot_companies: List HubSpot companies with pagination | get_hubspot_company: Get full details for a HubSpot company by ID | get_hubspot_deal: Get full details for a HubSpot deal by ID | get_leadconnector_location_info: Get metadata for the authenticated LeadConnector sub-account (location): name, address, phone, email, timezone, and plan | get_leadconnector_contact: Get full details for a single LeadConnector contact by ID, including custom fields and tags | search_leadconnector_contacts: Search LeadConnector contacts by name, email address, or phone number | list_leadconnector_opportunities: List opportunities (pipeline deals) in the connected LeadConnector location | get_leadconnector_opportunity: Get full details for a single LeadConnector opportunity (deal) by ID | list_leadconnector_calendars: List all calendars configured in the connected LeadConnector location | list_leadconnector_appointments: List calendar appointments (events) in the connected LeadConnector location, optionally filtered by date range | list_leadconnector_conversations: List conversation threads (SMS, email, calls) in the connected LeadConnector location | get_leadconnector_conversation: Get a LeadConnector conversation thread by ID, including the full message history | list_leadconnector_payments: List payment orders for the connected LeadConnector location | list_leadconnector_forms: List forms configured in the connected LeadConnector location
paramsNoAction-specific parameters. list_hubspot_contacts: {limit?: integer, vid_offset?: integer} | search_hubspot_contacts: {query: string, limit?: integer} | list_hubspot_deals: {limit?: integer, offset?: integer} | list_leadconnector_contacts: {limit?: integer, query?: string} | get_hubspot_account_info: none | get_hubspot_contact: {contact_id: integer} | list_hubspot_companies: {limit?: integer, offset?: integer} | get_hubspot_company: {company_id: integer} | get_hubspot_deal: {deal_id: integer} | get_leadconnector_location_info: none | get_leadconnector_contact: {contact_id: string} | search_leadconnector_contacts: {query: string, limit?: integer} | list_leadconnector_opportunities: {pipeline_id?: string, limit?: integer, skip?: integer} | get_leadconnector_opportunity: {opportunity_id: string} | list_leadconnector_calendars: none | list_leadconnector_appointments: {start_date?: string, end_date?: string, limit?: integer} | list_leadconnector_conversations: {limit?: integer, last_message_after?: string} | get_leadconnector_conversation: {conversation_id: string} | list_leadconnector_payments: {limit?: integer, skip?: integer, start_date?: string, end_date?: string} | list_leadconnector_forms: {limit?: integer, skip?: integer}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes beyond that by disclosing the 15-minute provenance-token window, replica-agnostic reuse, the unverified_model_data fallback, and a data accuracy contract — genuinely useful operational context that is consistent with the read-only annotations.

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?

Purpose is front-loaded in the first sentence, but the bulk of the text is cross-cutting governance for chart_render, provenance tokens, attribution footers, and data contracts rather than this connector's own behavior. Much of it likely duplicates instructions carried by chart_render, making it verbose for what it adds here.

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 20-action connector with no output schema, the enum descriptions carry the action-level detail and the description carries the behavioral contract. It is fairly complete, though it never characterizes the shape or format of returned records, which is the main remaining gap.

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%: the action enum and the params object document every action and its arguments in detail. The description adds no parameter-level syntax or constraints beyond that, so the baseline 3 for schema-driven documentation 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?

The first sentence names a specific domain (CRM across HubSpot and LeadConnector) and enumerates the resources covered: contacts, deals, pipelines, companies, opportunities. This distinguishes it from sibling CRM connectors like salesforce_connector or close_connector. The multi-action verb itself is vague, but the enum supplies the specific operations.

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?

The description gives rich guidance on downstream behavior (when to call chart_render, provenance token reuse) but never states when to select this connector over alternatives such as salesforce_connector or podium_connector. Usage is implied by the named CRMs rather than explicitly routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.