Skip to main content
Glama
Sign In
honeybook-mcp

honeybook-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_message

Read-only

Retrieve one HoneyBook message in full, including body, sender, recipients, attachments, and per-recipient delivery status. Choose plain text, Markdown, or original HTML.

Instructions

Read one message in full: body (HoneyBook's plain text by default, Markdown, or the original HTML), sender, recipients, attachments and per-recipient delivery status.

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": {
      "workspace_id": "<workspace_id>",
      "message_id": "<message_id>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoBody format: "text" (default, HoneyBook's plain text), "markdown" (keeps lists, paragraphs and links with their address, which the plain text loses; tracking pixels and hidden text dropped) or "html" (the original, raw).
originNoPortal origin (e.g. https://<vendor>.hbportal.co). Optional when only one session is active.
message_idYesThe message _id from list_messages.
workspace_idYesThe workspace _id (from list_projects, or .workspace._id on any workspace_file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / properties / format / description
      Previous value: -"Body format. Default \"text\"."New value: +"Body format: \"text\" (default, HoneyBook's plain text), \"markdown\" (keeps lists, paragraphs and links with their address, which the plain text loses; tracking pixels and hidden text dropped) or \"html\" (the original, raw)."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "text",
-  "html"
-]New value: +[
+  "text",
+  "markdown",
+  "html"
+]
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv0.9.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the returned payload, including per-recipient delivery status, but says nothing about session/origin ambiguity, permissions, or truncation of large bodies or attachments.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and scope, with the return payload listed after the colon. No filler and nothing buried.

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 read-only single-record fetch with full schema coverage and no output schema, the description compensates well by naming the returned fields. It stops short of covering edge behavior such as what happens with multiple active sessions or very large attachments, but nothing essential is missing.

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 coverage is 100% and the format enum is already fully explained in the schema, including the note that plain text loses link addresses. The description's parenthetical about text/Markdown/HTML restates that, so it adds little beyond the structured field.

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?

"Read one message in full" gives a specific verb and a precisely scoped resource, then enumerates exactly what comes back (body, sender, recipients, attachments, per-recipient delivery status). The scope word "one" cleanly separates it from list_messages without needing to name it.

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?

The description never says when to choose this over list_messages, mark_messages_seen, or list_attachments, and offers no prerequisites or exclusions. The only routing hint (message_id comes from list_messages) lives in the schema, not the description.

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