Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_conversation_cancel_scheduled_email_message

DestructiveIdempotent

Cancels a scheduled email message by deleting it using the provided emailMessageId, preventing the message from being sent at its scheduled time.

Instructions

Cancel a scheduled email message. Post the messageId for the API to delete a scheduled email message. Endpoint: DELETE /conversations/messages/email/{emailMessageId}/schedule (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations/message.write

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emailMessageId": "<emailMessageId>"
    },
    "name": "ghl_conversation_cancel_scheduled_email_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailMessageIdYesEmail Message Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context (DELETE endpoint path, v3 version header, OAuth scope conversations/message.write), but says nothing about irreversibility or what a caller sees after cancellation.

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 purpose is front-loaded in one clean sentence, but the remainder carries a stray '<br />' artifact and endpoint/source metadata that reads like generated boilerplate. Useful for a developer, marginal for an agent choosing a tool.

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 one-parameter destructive operation with full annotation coverage and no output schema, the description supplies enough: what it does, the endpoint, and the required OAuth scope. Only the relationship to the generic cancel sibling is left implicit.

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?

With 100% schema coverage on a single parameter, the schema already documents emailMessageId with an example, so baseline 3 applies. The description's use of 'messageId' rather than 'emailMessageId' adds no semantics and slightly muddies the mapping to the actual parameter name.

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 opening sentence states a specific verb+resource (cancel a scheduled email message), and the name/description scope it to email rather than the generic sibling ghl_conversation_cancel_scheduled_message. It stops short of explicitly contrasting with that sibling, but the resource specificity is enough to locate the tool.

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?

There is no when-to-use/when-not-to-use guidance and no reference to the near-identical sibling ghl_conversation_cancel_scheduled_message, so an agent must infer selection from the name alone. The instruction 'Post the messageId' is a mechanics note, not usage guidance.

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

Deploy Server

Other Tools