webex-mcp

by yuryev89

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

webex_create_webhook

Create a Webex webhook to post selected resource events to a target URL for real-time notifications.

Instructions

Create event webhook.

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": {
      "name": "<name>",
      "targetUrl": "<targetUrl>",
      "resource": "<resource>",
      "event": "<event>"
    },
    "name": "webex_create_webhook"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Webhook name
`event`	Yes	Event (created/updated/deleted)
`filter`	No	Filter (e.g. roomId=...)
`secret`	No	Signature secret
`resource`	Yes	Resource (e.g. messages)
`targetUrl`	Yes	Event POST URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the mutation implied by "create". It does not mention that a webhook begins firing immediately after creation, whether duplicate subscriptions are allowed, what secrets/signature behavior involves, or what permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The three-word description contains no wasted wording and is front-loaded with the verb, but its brevity reflects under-specification rather than disciplined concision. It is a fragment that leaves the substantive information about the operation unsaid.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, four-required mutation tool with no annotations and no output schema, the description is far too thin. It should at minimum explain the resource/event pairing semantics, the role of targetUrl and secret, and what a successful creation returns, none of which appear.

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 description coverage is 100%, so all six parameters (name, event, filter, secret, resource, targetUrl) are already documented in the schema, which establishes the baseline of 3. The description adds no additional meaning such as valid resource/event combinations or filter syntax, so it cannot exceed the baseline.

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

Purpose3/5

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

"Create event webhook" states a specific verb (create) and resource (webhook), so the basic operation is identifiable. However, it gives no scope or distinguishing detail against the four sibling webhook tools (list/get/update/delete), nor does it indicate what an event webhook subscription means in Webex terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says this is for subscribing an HTTP endpoint to Webex events, when to prefer this over update_webhook, or what prerequisites (a reachable targetUrl, valid resource/event pairing) must hold. The agent must infer everything from the parameter names.

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

Deploy Server