Skip to main content
Glama
calypsoCodex

HubSpot MCP Extended

by calypsoCodex

post-crm-v3-objects-objtype-batch-create_create

Batch-create CRM objects for any object type. Supply an array of inputs with property values to create multiple records in one API call.

Instructions

Create a batch of objects. REQUIRES body parameter with objects to create. Example: {body: {inputs: [{"properties": {"firstname": "John", "lastname": "Doe", "email": "john@example.com"}}]}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsYesArray of items
objectTypeYesPath parameter objectType
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'create' and gives an example, but does not mention return formats, partial success behavior, limits, or error handling.

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?

The description is concise and front-loaded with the main action. The example is somewhat long but serves a clear purpose. No redundant sentences.

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?

This is a complex batch creation tool with nested associations in the schema, but the description does not mention important context like including associations, response details, or rate limits. The schema covers parameters, but the description adds little operational context.

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%, so the baseline is 3. The example adds some meaning by showing the structure, but it introduces ambiguity by showing a 'body' wrapper that doesn't align with the schema's top-level 'inputs' parameter.

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 description clearly states the action ('Create a batch of objects') with a specific verb and resource. It differentiates from read/update/archive siblings by explicitly saying 'create', though it doesn't explicitly contrast with batch-upsert or v4 variants.

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 about when to use this tool versus alternatives like batch-upsert or batch-update. The only guidance is a requirement about the body parameter, not contextual usage.

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

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