Skip to main content
Glama
ZLeventer

hubspot-mcp

hs_list_forms

List all HubSpot forms ordered by most recently updated, with optional limit on number of forms returned. Helps track form activity and changes.

Instructions

List all HubSpot forms ordered by most recently updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • The `listForms` handler function that calls the HubSpot API to list forms, accepting an optional `limit` and sorting by `updatedAt` descending.
    export async function listForms(args: z.infer<typeof ListFormsSchema>) {
      return hubspot("/forms/v2/forms", "GET", undefined, {
        limit: args.limit ?? 20,
        orderBy: "updatedAt",
        direction: "desc",
      });
    }
  • The `ListFormsSchema` defining input validation: optional `limit` (int 1-50, default 20).
    export const ListFormsSchema = z.object({
      limit: z.number().int().min(1).max(50).default(20).optional(),
    });
  • src/index.ts:241-246 (registration)
    Registration of the "hs_list_forms" tool using `server.tool()` with description and schema.
    server.tool(
      "hs_list_forms",
      "List all HubSpot forms ordered by most recently updated.",
      ListFormsSchema.shape,
      async (args) => { try { return ok(await listForms(args)); } catch (e) { return err(e); } },
    );
  • Import of `ListFormsSchema` and `listForms` from the forms tool module.
    import {
      ListFormsSchema, listForms,
      GetFormSchema, getForm,
      FormSubmissionsSchema, formSubmissions,
    } from "./tools/forms.js";
Behavior2/5

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

No annotations exist, so the description carries full burden. It only states the ordering behavior but does not disclose whether the operation is read-only, authentication needs, rate limits, or pagination details.

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 a single sentence, which is concise, but it lacks structure and additional context. While not verbose, it could be improved by front-loading key details.

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

Completeness2/5

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

Given the simple tool with one parameter and no output schema, the description is too minimal. It does not explain the return format or how the 'limit' parameter affects results, leaving gaps for the agent.

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

Parameters1/5

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

Schema description coverage is 0%, meaning no parameter descriptions are provided in the schema. The description adds no information about the 'limit' parameter, leaving the agent without guidance on its usage.

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?

The description clearly states the verb 'list', the resource 'HubSpot forms', and adds a specific ordering detail 'ordered by most recently updated'. This distinguishes it from sibling list tools like hs_list_lists.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context for when this tool is appropriate.

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

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