Skip to main content
Glama
ajaystream

HubSpot MCP Server

by ajaystream

hubspot-generate-feedback-link

Read-onlyIdempotent

Generate a feedback link to report issues or suggest improvements for HubSpot MCP tools, helping developers enhance functionality.

Instructions

🎯 Purpose:
  1. Use this tool when the user wants to submit feedback about HubSpot MCP tool.
  2. Use this tool proactively when the other HubSpot MCP tools are unable to solve the user's tasks effectively.
  3. Use this tool when you sense dissatisfaction from the user using HubSpot MCP tools.
  4. Feedback will help us improve the HubSpot MCP tools in future iterations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The process method implements the core logic of the tool, constructing a message with the HubSpot feedback URL and returning it as structured content.
    async process(args) {
        const feedbackUrl = 'https://developers.hubspot.com/mcp';
        const message = `Share Feedback link with the user and ask the user to provide feedback: ${feedbackUrl}`;
        return {
            content: [
                {
                    type: 'text',
                    text: message,
                },
            ],
        };
    }
  • Defines the Zod input schema (empty object) and ToolDefinition object containing the tool name, description, inputSchema, and annotations.
    // Define schema for the feedback tool
    const FeedbackLinkSchema = z.object({});
    const ToolDefinition = {
        name: 'hubspot-generate-feedback-link',
        description: `
        🎯 Purpose:
          1. Use this tool when the user wants to submit feedback about HubSpot MCP tool.
          2. Use this tool proactively when the other HubSpot MCP tools are unable to solve the user's tasks effectively.
          3. Use this tool when you sense dissatisfaction from the user using HubSpot MCP tools.
          4. Feedback will help us improve the HubSpot MCP tools in future iterations.
      `,
        inputSchema: zodToJsonSchema(FeedbackLinkSchema),
        annotations: {
            title: 'Generate Feedback Link',
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false,
        },
    };
  • Registers an instance of FeedbackLinkTool with the tool registry.
    registerTool(new FeedbackLinkTool());
  • Imports the FeedbackLinkTool class for registration.
    import { FeedbackLinkTool } from './links/feedbackLinkTool.js';
Behavior4/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds context about proactive use and feedback purpose, which enhances understanding beyond annotations. No contradiction with 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?

The description is structured with bullet points but includes repetitive elements (e.g., multiple 'Use this tool' phrases) and could be more front-loaded. It's appropriately sized but not maximally efficient.

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?

Given 0 parameters, no output schema, and rich annotations, the description is complete enough for a feedback tool. It covers purpose, usage, and context adequately, though it could briefly mention the feedback mechanism (e.g., link generation).

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?

There are 0 parameters, and schema description coverage is 100%. The description doesn't need to explain parameters, so a baseline of 4 is appropriate as it focuses on usage rather than input details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose is to generate a feedback link for HubSpot MCP tools, which is clear but not specific about the verb+resource combination. It distinguishes from siblings by focusing on feedback rather than data operations, but lacks explicit differentiation in terms of functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage scenarios: when the user wants to submit feedback, when other tools fail, or when sensing user dissatisfaction. It clearly outlines when to use this tool versus alternatives, with specific context and exclusions.

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/ajaystream/hubspot-mcp-custom'

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