OwnerRez MCP Server

list_webhook_subscriptions

List all active webhook subscriptions on your OwnerRez account to monitor and manage integrations.

Instructions

List active webhook subscriptions on the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_webhook_subscriptions"
  }
}

Input Schema

Name	Required	Description	Default
`max_items`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 23, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations exist, so the description bears the responsibility for behavioral disclosure. It does not state whether the operation is read-only, if there are side effects, permissions required, or any limitations. The only implied behavior is that it lists active subscriptions, but this is part of the purpose rather than a transparency trait.

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

Conciseness5/5

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

The description is a single, concise sentence with no redundant words. It directly states the action and scope, achieving high efficiency.

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 simple list operation with one parameter, the description is too sparse. It does not explain the return format, the meaning of max_items, or any caveats. Even though the sibling tools are clear, the missing parameter semantics and behavioral details make the description incomplete.

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

Parameters1/5

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

The only parameter, max_items, is described only by its schema (integer, default 200). The description provides no explanation of its meaning or effect, and since schema coverage is 0%, the description fails to compensate. The purpose of max_items is not inferable from the minimal description.

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 clearly states the verb 'List' and the resource 'webhook subscriptions', further scoped by 'active' and 'on the account'. This distinguishes it from sibling tools like create_webhook_subscription and delete_webhook_subscription.

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?

The purpose is clear enough to infer when to use this tool versus creating or deleting subscriptions, but it does not explicitly mention alternatives or exclusions. The context is clear but lacks explicit guidance.

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

Deploy Server