get_webhookGet a webhook by ID without revealing its signing secret.
| Name | Required | Description | Default |
|---|---|---|---|
| webhook_id | Yes | ||
| organization_id | No | Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | The requested webhook without its signing secret. |
Changes observed during successful MCP inspections.
Input schema / properties / organization_idAdded value: +{
+ "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / webhook_id / patternAdded value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / result / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / signing_secret / $refRemoved value: -"#/properties/result/properties/study_id"Output schema / properties / result / properties / signing_secret / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / result / properties / updated_at / $refRemoved value: -"#/properties/result/properties/created_at"Output schema / properties / result / properties / updated_at / descriptionAdded value: +"ISO 8601 timestamp."Output schema / properties / result / properties / updated_at / typeAdded value: +[
+ "string",
+ "null"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description nonetheless adds a genuine behavioral fact beyond annotations: the signing secret is deliberately redacted from the response, which matters for downstream handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler; every clause carries information (verb, resource, key constraint).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and annotations cover safety. However, the description omits when to use this versus list_webhooks and says nothing about the organization_id parameter, leaving gaps for an agent calling the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%, with webhook_id required but undocumented in the schema while organization_id carries a description. The description only implies the ID lookup and adds nothing about organization_id's admin-only semantics. Baseline 3 is appropriate given the partial coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get a webhook by ID') so the agent knows exactly what it does. It implicitly contrasts with sibling list_webhooks, but does not name or differentiate against other webhook siblings such as get_external_panel or list_webhook_deliveries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no prerequisites, and no alternatives such as list_webhooks for discovering an ID. The only usage signal is the word 'ID', leaving the agent to infer everything else.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.