Skip to main content
Glama

Save a webhook

save_webhook
Destructive

Create (omit webhook_id) or update a webhook endpoint (admin only; Solo Lite 1 endpoint, Solo 3, Team and Business+ 10). md2sign POSTs signed JSON with the document, its markdown and, on document.completed, the signed PDF as base64 to a public https URL such as Zapier, Make or n8n. Set send_test=true to send a test event.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic https:// URL. Required when creating.
eventsNoDefaults to ["document.completed"].
api_keyNoAn md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an "Authorization: Bearer <api_key>" header.
is_activeNoSet false to pause deliveries without deleting the endpoint. Default true.
send_testNoQueue a webhook.test delivery after saving.
webhook_idNoOmit to create a new endpoint.
descriptionNoLabel for this endpoint, e.g. "Send signed contracts to HubSpot".
include_pdfNoAttach the signed PDF (base64) to document.completed. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your md2sign API key. Only needed if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."New value: +"An md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."
  2. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"Label for this endpoint, e.g. \"Send signed contracts to HubSpot\"."
    • addedInput schema / properties / is_active / description
      Added value: +"Set false to pause deliveries without deleting the endpoint. Default true."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond the annotations: admin-only access, per-plan endpoint limits, that md2sign POSTs signed JSON with document markdown and base64 PDF on document.completed, and that the target must be a public https URL. It does not explain the destructiveHint=true / idempotentHint=false implications, i.e. whether an update overwrites or clears unspecified fields, nor whether a signing secret is issued.

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?

Front-loaded with the create/update decision, and every sentence carries information. The middle sentence is long and packs payload format, examples, and the https/public requirement together, which slightly hurts scannability but wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no output schema, the description covers access rules, plan limits, and delivery payload. It omits what a save returns (endpoint id, signing secret) and how updates treat unspecified fields, which an agent needs to chain calls correctly.

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 every parameter is already documented in structured form; the description largely restates the webhook_id omission rule and send_test behavior. It adds only marginal meaning, such as example integrations (Zapier, Make, n8n) for the url parameter.

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 verb+resource pair ("Create ... or update a webhook endpoint") and disambiguates the two modes with a concrete rule: omit webhook_id to create. An agent immediately knows this is the write path for webhook endpoints, distinct from list_webhooks/delete_webhook siblings.

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

Usage Guidelines4/5

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

Gives explicit when-to-create vs when-to-update guidance plus constraints (admin only, plan-tier endpoint caps, send_test for verification). It stops short of routing to alternatives, e.g. telling the agent to call list_webhooks to obtain a webhook_id before updating or delete_webhook to remove an endpoint.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.