RD Station

rdstation_webhooks_list

Webhooks da RD Station Marketing. Ações:

list: lista webhooks configurados.
create: cria um webhook (passe 'webhook' com url, event_type, entity_type…).
delete: remove um webhook (requer uuid).

[Flattened action: list]

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": "rdstation_webhooks_list"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	No
`account`	No
`webhook`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

D1.3/5.0

Behavior1/5

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

The description includes both read (list) and write (create, delete) actions, while annotations set readOnlyHint: false and destructiveHint: false, implying the tool is neither read-only nor destructive. This is contradictory. The description fails to disclose that only the list action is intended.

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

Conciseness2/5

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

The description is short but contains irrelevant details (create/delete) for a tool meant to list. The structure is not front-loaded for the list purpose; the vital info ('[Flattened action: list]') is at the end.

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

Completeness1/5

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

No output schema, no return format. The description provides no context on how listing works, what filters apply (if any), or pagination. For a tool with nested objects and zero schema coverage, this is severely 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?

Schema description coverage is 0%, and the description provides no explanation of parameters for the list action. The create/delete parameter hints are irrelevant. The parameters uuid, account, and webhook remain unexplained for listing.

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

Purpose2/5

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

The tool name suggests a listing action, but the description enumerates three actions (list, create, delete) without clearly indicating that only 'list' is valid for this tool. The '[Flattened action: list]' note at the end attempts to clarify, but the preceding instructions for create and delete cause confusion.

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

Usage Guidelines1/5

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

No guidance is given on when to use this tool versus siblings like rdstation_webhooks_create or rdstation_webhooks_delete. Instead, the description includes create/delete instructions, misleading the agent into thinking it can perform those actions here.

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

All RD Station tools Inspect

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.