Skip to main content
Glama

pm_create_webhook

Create an outgoing webhook subscription for the current workspace. Every delivery is signed with HMAC-SHA256 of the raw body using the webhook secret, sent as X-Webhook-Signature-256: sha256=<hex>. Pass your own secret, or omit it and this tool generates one and returns it as secret in the result. SAVE THE SECRET IMMEDIATELY: pm_get_webhook / pm_list_webhooks never return it; to rotate it, pass a new secret to pm_update_webhook. Event types: Project Management events are dash-cased (e.g. "task-created", "task-status-changed", "comment-added"); wiki (Codexum) events are dotted and start with "wiki." (e.g. "wiki.page.published", "wiki.comment.added"); feature-request (Roadmarq) events start with "feedback." (e.g. "feedback.request.created", "feedback.bug.created"). Call pm_list_webhook_event_types for the full list with each type's product and allowed scopes. An unscoped webhook may mix products. Optionally narrow delivery to one entity with scopeType plus scopeEntityIdentifier: SPACE / FOLDER / TASK_LIST / TASK (identifier), WIKI_SPACE (space key), WIKI_PAGE (page id; covers its descendants), FEEDBACK_BOARD (board slug or id; stored and listed as the board UUID), FEEDBACK_REQUEST / FEEDBACK_BUG (short key such as "FR-12", or id); omit both for workspace-wide delivery. A scoped webhook may only list event types of its scope's product. Wiki and feature-request events need the API key to hold that product's read scope, and every delivery is re-checked: an event is sent only while the webhook creator can still see the item. Security bugs are not delivered to webhooks created with an API key: includeSecurityBugs can only be turned on by a workspace admin signed in as a person. Envelope: {version, id, type, timestamp, workspaceIdentifier, source ("pm" | "codexum" | "roadmarq"), eventId (stable across webhooks and replays; use it to de-duplicate), data}. Payloads are thin: no content bodies, comment text or emails. Retries fire at +0s / +1min / +5min (3 attempts total) and treat both 4xx and 5xx as failures. The URL must be publicly reachable: Dutify refuses private, loopback, link-local, CGNAT and IPv6 ULA addresses, localhost, bare hostnames and *.svc / *.cluster.local names (400 WEBHOOK_URL_NOT_ALLOWED) at create, update and resume, and re-checks it on every attempt. Redirects are not followed; http:// is accepted for public addresses. API-key scope: webhooks: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": {
      "url": "<url>",
      "eventTypes": "<eventTypes>"
    },
    "name": "pm_create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS endpoint that will receive POSTs
nameNoHuman-readable label for the webhook
secretNoOptional HMAC signing secret; omit it to get a generated one, returned once
accountNoMulti-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
scopeTypeNoOptional scope narrowing; requires scopeEntityIdentifier when set
workspaceNoWorkspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.
eventTypesYesEvent names from pm_list_webhook_event_types, e.g. ["task-created", "wiki.page.published", "feedback.request.created"]
scopeEntityIdentifierNoThe scoped entity: its identifier, a wiki space key, a board slug or id, or a request/bug short key (required when scopeType is set; requires scopeType)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scopeEntityIdentifier / description
      Previous value: -"The scoped entity: its identifier, a wiki space key, a board slug, or a request/bug short key (required when scopeType is set)"New value: +"The scoped entity: its identifier, a wiki space key, a board slug or id, or a request/bug short key (required when scopeType is set; requires scopeType)"
  2. Changed5 schema fields changed
    • changedInput schema / properties / eventTypes / description
      Previous value: -"Dash-cased event names, e.g. [\"task-created\", \"comment-added\"]"New value: +"Event names from pm_list_webhook_event_types, e.g. [\"task-created\", \"wiki.page.published\", \"feedback.request.created\"]"
    • changedInput schema / properties / scopeEntityIdentifier / description
      Previous value: -"Identifier of the scoping entity (required when scopeType is set)"New value: +"The scoped entity: its identifier, a wiki space key, a board slug, or a request/bug short key (required when scopeType is set)"
    • changedInput schema / properties / scopeType / enum
      Previous value: -[
      -  "SPACE",
      -  "FOLDER",
      -  "TASK_LIST",
      -  "TASK"
      -]New value: +[
      +  "SPACE",
      +  "FOLDER",
      +  "TASK_LIST",
      +  "TASK",
      +  "WIKI_SPACE",
      +  "WIKI_PAGE",
      +  "FEEDBACK_BOARD",
      +  "FEEDBACK_REQUEST",
      +  "FEEDBACK_BUG"
      +]
    • addedInput schema / properties / secret
      Added value: +{
      +  "description": "Optional HMAC signing secret; omit it to get a generated one, returned once",
      +  "type": "string"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"HTTPS endpoint that will receive POSTs"New value: +"Public HTTPS endpoint that will receive POSTs"
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Far exceeds the annotations (readOnly=false, destructive=false, openWorld=true, idempotent=false) with concrete behavior: HMAC-SHA256 signing header format, secret returned only once, URL reachability refusals with error code, retry schedule (+0s/+1min/+5min), redirect non-following, per-delivery permission re-checks, and the API-key security-bug restriction.

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 core action and signing contract, and every section carries real information. It is a dense block of prose, though; splitting the envelope/retry/URL details into short structured clauses would ease scanning without losing content.

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

Completeness5/5

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

Given 8 parameters, multi-product events, security implications, and no output schema, the description covers everything an agent needs: the delivery envelope shape (version/id/type/timestamp/source/eventId/data), thin payloads, retry and URL-validation rules, and secret lifecycle.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description still enriches meaning: it explains scopeType+scopeEntityIdentifier combinations and identifier formats per type (space key, page id covering descendants, board slug/id stored as UUID, short keys like FR-12), plus the unscoped-vs-scoped product restriction that the enum alone cannot convey.

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?

Opens with a specific verb+resource: 'Create an outgoing webhook subscription for the current workspace.' It is clearly distinguishable from siblings like pm_get_webhook, pm_update_webhook, and pm_list_webhooks, which it explicitly names later for secret rotation and listing.

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

Usage Guidelines5/5

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

Explicitly routes the agent: pass your own secret or omit for a generated one, use pm_update_webhook to rotate, call pm_list_webhook_event_types for the full event list, and omit scopeType/scopeEntityIdentifier for workspace-wide delivery. Alternatives and conditions are stated, not inferred.

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.

Resources