Skip to main content
Glama

Groundbase

by com.groundbasecrm.mcp
OverviewDiscussionsAdmin

inbound_webhooks_manage

Destructive

Inbound webhooks: URLs other services POST to so Groundbase creates contacts, deals, tasks etc. action list | get | create | update | delete. create returns the full URL with its token ONCE (tell the user; it cannot be shown again). delete stops the URL accepting posts immediately; confirm first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFor get/update/delete.
nameNoRequired on create.
actionYes
isActiveNoUpdate only; false pauses receiving.
descriptionNo
ipAllowlistNoCIDRs. Empty = any IP.
mappingJsonNoFor mappingMode "mapped": { "actions": [{ "event": "contact.find_or_create" (or another native event), "fields": { "<groundbase_field>": "<path.in.payload>" }, "static": { "<groundbase_field>": <literal> } }] }. Paths are dotted with optional indices ("lead.contact[0].email"); missing paths are omitted.
mappingModeNoDefault native.
signingSecretNoOptional HMAC secret (create only); senders send X-Groundbase-Signature.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 / id / description
      Previous value: -"Inbound webhook UUID. Required for get/update/delete."New value: +"For get/update/delete."
    • changedInput schema / properties / ipAllowlist / description
      Previous value: -"Optional CIDR list. Empty = any IP."New value: +"CIDRs. Empty = any IP."
    • changedInput schema / properties / isActive / description
      Previous value: -"Pause receiving by setting to false (update only)."New value: +"Update only; false pauses receiving."
    • changedInput schema / properties / mappingJson / description
      Previous value: -"Required when mappingMode=\"mapped\". Translates an arbitrary inbound payload into native Groundbase actions. Shape: { \"actions\": [{ \"event\": \"contact.find_or_create\" | \"contact.create\" | \"contact.update\" | \"company.find_or_create\" | \"company.create\" | \"deal.create\" | \"note.create\" | \"task.create\" | \"tag.apply\" | \"tag.remove\", \"fields\": { \"<groundbase_field>\": \"<jsonpath.in.payload>\", ... }, \"static\": { \"<groundbase_field>\": <literal>, ... } }] }. Paths are dot-separated with optional bracketed array indices (e.g. \"lead.contact[0].email\" or equivalently \"lead.contact.0.email\"). Missing paths resolve to undefined and are omitted. Example for a Facebook Lead Ads webhook: { \"actions\": [{ \"event\": \"contact.find_or_create\", \"fields\": { \"first_name\": \"name.first\", \"email\": \"email\", \"phone\": \"phone\" }, \"static\": { \"source\": \"fb-lead-ads\", \"tags\": [\"lead\"] } }] }."New value: +"For mappingMode \"mapped\": { \"actions\": [{ \"event\": \"contact.find_or_create\" (or another native event), \"fields\": { \"<groundbase_field>\": \"<path.in.payload>\" }, \"static\": { \"<groundbase_field>\": <literal> } }] }. Paths are dotted with optional indices (\"lead.contact[0].email\"); missing paths are omitted."
    • changedInput schema / properties / mappingMode / description
      Previous value: -"Default \"native\" on create."New value: +"Default native."
    • changedInput schema / properties / name / description
      Previous value: -"Display name. Required on create."New value: +"Required on create."
    • changedInput schema / properties / signingSecret / description
      Previous value: -"Optional HMAC secret (create only). Senders include X-Groundbase-Signature."New value: +"Optional HMAC secret (create only); senders send X-Groundbase-Signature."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds material context beyond them: the signing/token URL is returned only once and cannot be reshown, and delete immediately stops the endpoint from accepting posts. These are non-obvious behavioral traits an agent must communicate.

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?

Dense and front-loaded: identity/scope first, then the action list, then critical caveats. Nearly every clause earns its place, though the multi-clause second half could be slightly tighter.

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?

For a complex 9-param tool with nested mapping objects and no output schema, the description covers the highest-risk behaviors (one-time token, destructive delete). It leaves ipAllowlist/mapping semantics to the well-documented schema, which is reasonable.

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 78%, near the high-coverage baseline, and the nested mappingJson/mappingMode fields are already documented in the schema. The description contributes no additional parameter meaning beyond restating the action set, so the 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 verb+resource ('Inbound webhooks: URLs other services POST to so Groundbase creates contacts, deals, tasks') and enumerates the operations. It also implicitly distinguishes itself from the sibling outbound_webhooks_manage by naming the inbound direction.

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?

Per-action guidance is present ('create returns the token ONCE', 'delete ... confirm first'), which helps the agent act correctly. However, there is no explicit when-to-use/when-not guidance versus alternatives such as outbound_webhooks_manage; usage is only implied.

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