Skip to main content
Glama

Create or change an outgoing webhook

dosai_save_webhook_integration
Destructive

Send the project's events to the owner's own program, Zapier or Make: create (name, url, events) or change one by integration_id (only what you pass changes). The address must be https. Events: lead_created, conversation_started, message_received, payment_received, ai_error, whatsapp_disconnected, instagram_disconnected, schedule_problem, tokens_low, trial_expiring, message_inbound, message_edited, message_deleted. Up to 20 per project. A new or changed address takes two steps: the owner confirms where clients' data will go. Check it with dosai_test_integration. Requires editor role.

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": "dosai_save_webhook_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
nameNo
typeNo
eventsNo
headersNoExtra request headers, e.g. a secret the receiver checks.
is_activeNo
project_idYesFrom dosai_list_projects.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.
integration_idNoOmit to create a new one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / integration_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: the write is destructiveHint=true, but the description explains that an update only changes the fields you pass, that the address must be https, the 20-per-project cap, the editor-role gate, and the two-step confirmation where the owner must approve where client data goes before the change lands. That is exactly the behavioral context an agent needs before mutating an integration.

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?

Purpose is front-loaded and sentences are dense with operational constraints. The one block of waste is the full thirteen-value event list, which duplicates the schema enum verbatim and could be shortened to a reference.

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?

For a 9-parameter mutation with a nested headers object, no output schema, and a confirmation handshake, the description covers the critical unknowns: prerequisites, quotas, transport constraints, merge semantics on update, and the next step to validate. Remaining gaps (is_active, headers) are secondary and partly covered by schema descriptions.

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 only 44%, and the description compensates partially: it explains name/url/events, integration_id as the create-vs-update switch, and the confirm flow. But it says nothing about is_active, headers, or how type (webhook/zapier/make) relates to the 'own program, Zapier or Make' phrasing, and it repeats the events enum already present in the schema rather than adding semantics.

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 concrete verb+resource and scope: send project events to the owner's own program, Zapier or Make, via an outgoing webhook. It then splits the two modes explicitly — create with (name, url, events) vs change by integration_id — so an agent knows which path it is on without opening the schema.

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 real operating context: editor role required, up to 20 per project, https-only address, and routes verification to dosai_test_integration. It explains the create-vs-update distinction clearly but never states the alternative for removal (e.g. a delete counterpart), so exclusions are left implicit.

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