Skip to main content
Glama
Sign In
honeybook-mcp

honeybook-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_project

Read-only

Fetch HoneyBook project details and participant contact/role info by project ID, returning event overview fields in compact or raw views.

Instructions

Project details — the portal's Overview "Project details" card plus the people on it: name, date, time, timezone, location, guest count, custom fields, cover image, and each participant's name / email / phone / role. view="raw" returns the untrimmed response (large: it embeds the vendor's account).

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "raw" returns the upstream payload unprojected. compact returns the Overview card plus participants; "raw" returns the untrimmed /details response, which embeds the vendor's whole account.
originNoPortal origin (e.g. https://<vendor>.hbportal.co). Optional when only one session is active.
project_idYesThe project (event) _id from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed2 schema fields changedv0.10.1
    • removedInput schema / properties / section
      Removed value: -{
-  "description": "Default \"summary\".",
-  "enum": [
-    "summary",
-    "raw"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"raw\" returns the upstream payload unprojected. compact returns the Overview card plus participants; \"raw\" returns the untrimmed /details response, which embeds the vendor's whole account.",
+  "enum": [
+    "compact",
+    "raw"
+  ],
+  "type": "string"
+}
  3. Addedv0.9.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral value by warning that view="raw" is large and embeds the vendor's whole account — useful for cost/context budgeting, though it says nothing about pagination or errors.

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?

Purpose and return contents are front-loaded, followed by the one non-obvious caveat about raw. Two sentences, no filler, no repetition of the name.

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?

No output schema exists, so the description carries the burden of describing the return shape — and it does, enumerating fields and the compact/raw difference. It omits error/empty-project behavior and session/origin prerequisites, which the schema only hints at.

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 schema already documents project_id, origin, and both view values including the 'embeds the vendor's account' caveat. The description's view="raw" note mostly restates the schema, so baseline 3 applies.

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?

States a specific resource (project details) and enumerates exactly what is returned — Overview card fields plus participants. An agent can distinguish it from list_projects, which is referenced in the schema's project_id description.

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

Usage Guidelines3/5

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

Usage is implied: fetch a single project by id, presumably after list_projects. There is no explicit when-to-use/when-not statement and no alternative tool is named, so the agent must infer the routing.

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