Skip to main content
Glama
Sign In

Groundbase

by com.groundbasecrm.mcp
OverviewDiscussionsAdmin

Manage outbound webhooks

outbound_webhooks_manage
Destructive

Outbound webhooks: Groundbase POSTs to a URL when subscribed events fire. action list | get | create | update | delete. create needs name, url, events and returns the signing secret ONCE (tell the user). create, or a new url, sends CRM data (names, emails, phones) there and emails the owner: confirm the url with the user first. delete stops deliveries and abandons retries; confirm first.

Input Schema

NameRequiredDescriptionDefault
idNoFor get/update/delete.
urlNoPublic http(s) URL (use https: the payload is CRM data). Required on create.
nameNoRequired on create.
actionYes
eventsNoEvent names, or ["*"] for all: contact|company.created/updated/deleted, contact.status_changed, deal.created/updated/deleted/stage_changed/won/lost, task.created/updated/completed/deleted, note.created, tag.applied/removed, sms.sent/received/delivered/failed, call.completed, voicemail.received, email.sent/received, invoice.issued/paid/voided, payment.recorded, quote.issued/accepted/declined, form.submitted, meeting.booked/rescheduled/cancelled. Slack and Discord webhook URLs get a readable message; others get signed JSON.
isActiveNoUpdate only; false pauses delivery.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / events / description
      Previous value: -"Event names, or [\"*\"] for all: contact|company.created/updated/deleted, deal.created/updated/deleted/stage_changed/won/lost, task.created/updated/completed/deleted, note.created, tag.applied/removed, sms.sent/received/delivered/failed, call.completed, voicemail.received, email.sent/received, invoice.issued/paid/voided, payment.recorded, quote.issued/accepted/declined, form.submitted, meeting.booked/rescheduled/cancelled. Slack and Discord webhook URLs get a readable message; others get signed JSON."New value: +"Event names, or [\"*\"] for all: contact|company.created/updated/deleted, contact.status_changed, deal.created/updated/deleted/stage_changed/won/lost, task.created/updated/completed/deleted, note.created, tag.applied/removed, sms.sent/received/delivered/failed, call.completed, voicemail.received, email.sent/received, invoice.issued/paid/voided, payment.recorded, quote.issued/accepted/declined, form.submitted, meeting.booked/rescheduled/cancelled. Slack and Discord webhook URLs get a readable message; others get signed JSON."
  2. Changed2 schema fields changed
    • changedInput schema / properties / events / description
      Previous value: -"Event names, or [\"*\"] for all: contact|company.created/updated/deleted, deal.created/updated/deleted/stage_changed/won/lost, task.created/updated/completed/deleted, note.created, tag.applied/removed, sms.sent/received/delivered/failed, call.completed, voicemail.received, email.sent, invoice.issued/paid/voided, payment.recorded. Slack and Discord webhook URLs get a readable message; others get signed JSON."New value: +"Event names, or [\"*\"] for all: contact|company.created/updated/deleted, deal.created/updated/deleted/stage_changed/won/lost, task.created/updated/completed/deleted, note.created, tag.applied/removed, sms.sent/received/delivered/failed, call.completed, voicemail.received, email.sent/received, invoice.issued/paid/voided, payment.recorded, quote.issued/accepted/declined, form.submitted, meeting.booked/rescheduled/cancelled. Slack and Discord webhook URLs get a readable message; others get signed JSON."
    • changedInput schema / properties / url / description
      Previous value: -"HTTPS. Required on create."New value: +"Public http(s) URL (use https: the payload is CRM data). Required on create."
  3. Changed7 schema fields changed
    • removedInput schema / properties / action / description
      Removed value: -"Which operation to run."
    • removedInput schema / properties / description / description
      Removed value: -"Optional longer-form context."
    • changedInput schema / properties / events / description
      Previous value: -"List of event names. Pass [\"*\"] for all events. Required on create."New value: +"Event names, or [\"*\"] for all: contact|company.created/updated/deleted, deal.created/updated/deleted/stage_changed/won/lost, task.created/updated/completed/deleted, note.created, tag.applied/removed, sms.sent/received/delivered/failed, call.completed, voicemail.received, email.sent, invoice.issued/paid/voided, payment.recorded. Slack and Discord webhook URLs get a readable message; others get signed JSON."
    • changedInput schema / properties / id / description
      Previous value: -"Subscription UUID. Required for get/update/delete."New value: +"For get/update/delete."
    • changedInput schema / properties / isActive / description
      Previous value: -"Pause delivery by setting to false (update only)."New value: +"Update only; false pauses delivery."
    • changedInput schema / properties / name / description
      Previous value: -"Short human-readable identifier, e.g. \"Slack #wins channel\". Required on create."New value: +"Required on create."
    • changedInput schema / properties / url / description
      Previous value: -"HTTPS URL Groundbase will POST to. Required on create."New value: +"HTTPS. Required on create."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds real context beyond them: the secret is returned ONCE, CRM data (names, emails, phones) is transmitted to the URL, the owner is emailed, and delete stops deliveries and abandons retries.

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 what a webhook is, then the action set, then per-action constraints. Dense and telegraphic but essentially every clause carries a decision the agent needs; the compression makes it slightly harder to parse than prose.

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?

Seven parameters, no output schema, destructive multi-action tool — yet the description covers lifecycle, prerequisites, side effects, and confirmation requirements. Nothing an agent needs to invoke it safely is missing.

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

Parameters4/5

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

At 71% schema coverage the schema already documents id, url, name, events, and isActive. The description reinforces which fields create requires (name, url, events) and adds payload-format nuance (Slack/Discord get readable messages, others signed JSON) that the schema also mentions but the summary elevates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (outbound webhooks) and mechanism (Groundbase POSTs to a URL on subscribed events), then enumerates the five actions. It is clearly distinct from inbound_webhooks_manage by the 'outbound' framing plus the POST-to-URL explanation, though it never names the sibling explicitly.

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?

Gives explicit operating rules: confirm the URL with the user before create or a URL change, confirm before delete, and tell the user the signing secret because it is returned only once. These are concrete when/when-not directives rather than inferred guidance.

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

All Groundbase toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources