Skip to main content
Glama

company create webhook

company_create_webhook
Idempotent

Create a Workspace subscription for post.published, post.failed, approval.decided or connection.changed. Approval decisions include all three outcomes and a stable envelope id for deduplication; publication results remain separate events. Requires settings permission and an approved public HTTP(S) receiver; backend validates destination safety, maximum 10 subscriptions. Active subscriptions send future events externally. No immediate test send. Save the one-time secret securely, never repeat it in routine summaries. 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>",
      "idempotencyKey": "<idempotencyKey>",
      "name": "<name>",
      "url": "<url>",
      "events": "<events>"
    },
    "name": "company_create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
eventsYes
isActiveNo
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 / events / items / enum
      Previous value: -[
      -  "post.published",
      -  "post.failed",
      -  "approval.decided"
      -]New value: +[
      +  "post.published",
      +  "post.failed",
      +  "approval.decided",
      +  "connection.changed"
      +]
    • changedInput schema / properties / events / maxItems
      Previous value: -3New value: +4
  2. Changed2 schema fields changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
      -  "post.published",
      -  "post.failed"
      -]New value: +[
      +  "post.published",
      +  "post.failed",
      +  "approval.decided"
      +]
    • changedInput schema / 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?

Beyond the annotations (openWorldHint, idempotentHint, non-destructive), the description discloses that subscriptions actively send future events externally, that there is no immediate test send, that a one-time secret is returned and must be stored and never repeated, and that retries must reuse the identical body and idempotencyKey. These are exactly the operational facts an agent needs and none are contradicted by the annotations.

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?

The purpose and event list are front-loaded, and nearly every clause carries distinct information (permissions, limits, secret handling, retry). It is dense and semicolon-packed, reading more like a checklist than a structured brief, but there is little outright waste.

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 mutating, open-world tool with six parameters and no output schema, the definition covers permissions, destination validation, subscription caps, secret handling, external delivery behavior, and retry semantics. Remaining gaps are minor: the exact response shape (where the secret appears) and the default/meaning of isActive are not described.

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 only 33% schema description coverage, the description carries real weight: it defines the semantics of 'events' by listing the four values, characterizes 'url' as an approved public HTTP(S) receiver subject to safety validation, and reinforces idempotencyKey retry behavior. 'name' and 'isActive' are left unaddressed, which keeps it from a 5.

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?

The description opens with a specific verb and resource ('Create a Workspace subscription') and enumerates the exact event types it can subscribe to (post.published, post.failed, approval.decided, connection.changed). Combined with the 'create' framing, an agent can distinguish this from company_update_webhook and company_delete_webhook without opening any 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?

It states concrete preconditions: settings permission required, an approved public HTTP(S) receiver, backend destination-safety validation, and a maximum of 10 subscriptions. It also gives retry guidance for a lost response. It stops short of explicitly naming alternatives (e.g., update vs. delete vs. regenerate-secret) or when-not-to-use cases, so it is clear context without full routing.

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.