Archive multiple HubSpot meetings simultaneously by specifying meeting IDs in a single request to remove outdated or completed meetings from your CRM.
Archive (delete) multiple meetings in a single request
| Name | Required | Description | Default |
|---|---|---|---|
| meetingIds | Yes |
Changes observed during successful MCP inspections.
v1.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions 'Archive (delete)' which implies destructive behavior, but doesn't clarify if deletion is permanent/reversible, what permissions are required, or how errors are handled for partial failures. For a batch destructive operation, this minimal disclosure is inadequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that communicates the core functionality without wasted words. It's appropriately sized for a straightforward tool, though it could benefit from additional context in subsequent sentences.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive batch operation with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't address critical aspects like error handling, confirmation requirements, or what happens to associated data. The agent lacks sufficient information to use this tool safely and effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It implies 'meetingIds' parameter through 'multiple meetings' but doesn't explain format, constraints, or maximum batch size. The description adds minimal value beyond what's inferable from the schema name, meeting the baseline for low coverage without fully compensating.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Archive (delete) multiple meetings') and resource ('meetings'), making the purpose immediately understandable. It distinguishes from the singular 'meetings_archive' sibling by specifying 'multiple meetings in a single request', though it doesn't explicitly contrast with other batch operations like 'meetings_batch_create' or 'meetings_batch_update'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing meeting IDs), compare with 'meetings_archive' for single deletions, or warn about irreversible deletion. With many sibling tools available, this lack of contextual guidance is a significant gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.