Skip to main content
Glama

company update webhook

company_update_webhook
DestructiveIdempotent

Change a Workspace webhook's name, approved receiver URL, publication, approval or connection events, or active state. Requires settings permission. Changing the URL or re-enabling starts a new connection-event baseline. Changing the URL or removing approval.decided cancels its pending decision deliveries; disabling also stops queued decision deliveries. This operation sends no test event and cannot set the signing secret. On a lost response retry the identical body and idempotencyKey.

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": {
      "workspaceId": "<workspaceId>",
      "webhookId": "<webhookId>",
      "idempotencyKey": "<idempotencyKey>",
      "changes": "<changes>"
    },
    "name": "company_update_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
webhookIdYesExact ID returned by a Company tool; never a personal platformId
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
idempotencyKeyYesStable visible-ASCII key, 1–255 characters, no comma/whitespace. On lost response retry the IDENTICAL body and key; never mint a new key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / changes / properties / events / items / enum
      Previous value: -[
      -  "post.published",
      -  "post.failed",
      -  "approval.decided"
      -]New value: +[
      +  "post.published",
      +  "post.failed",
      +  "approval.decided",
      +  "connection.changed"
      +]
    • changedInput schema / properties / changes / properties / events / maxItems
      Previous value: -3New value: +4
  2. Changed2 schema fields changed
    • changedInput schema / properties / changes / properties / events / items / enum
      Previous value: -[
      -  "post.published",
      -  "post.failed"
      -]New value: +[
      +  "post.published",
      +  "post.failed",
      +  "approval.decided"
      +]
    • changedInput schema / properties / changes / properties / events / maxItems
      Previous value: -2New value: +3
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint/idempotentHint/openWorldHint) by disclosing concrete side effects: a URL change or re-enable resets the connection-event baseline, a URL change or removal of approval.decided cancels pending decision deliveries, and disabling stops queued deliveries. It also flags that no test event is sent and prescribes the exact retry protocol (identical body and idempotencyKey) for a lost response.

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 can be changed, then permissions, then side effects, then limitations and retry guidance — a sensible order with no filler sentences. A few clauses ('Changing the URL or removing approval.decided cancels its pending decision deliveries') are dense enough to need a second read.

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 destructive, permission-gated mutation with a nested changes object and no output schema, it covers the essentials: authorization, side effects, what it cannot do, and failure/retry handling. The only material omission is partial-update semantics for the 'changes' object.

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?

With 75% schema coverage, the description still adds meaning by naming which fields inside the nested 'changes' object are mutable and by reinforcing the idempotencyKey retry contract. It does not clarify whether omitted fields inside 'changes' are left untouched, which is the one remaining semantic gap.

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 ('Change') plus the exact resource (Workspace webhook) and enumerates every mutable field (name, receiver URL, publication/approval/connection events, active state). That enumeration makes it unmistakable against siblings like company_create_webhook, company_delete_webhook, and company_regenerate_webhook_secret.

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 a clear precondition ('Requires settings permission') and an implicit routing rule: 'cannot set the signing secret' tells the agent to use the regenerate-secret sibling instead. It stops short of explicitly naming any sibling or stating when-not to use it, so it is strong context rather than full routing guidance.

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.